Searched hist:"2247 f48941743cab420394b5ff0fc65ec8c69a99" (Results 1 – 3 of 3) sorted by relevance
| /freebsd/sys/sys/ |
| H A D | aio.h | diff 2247f48941743cab420394b5ff0fc65ec8c69a99 Sun Jan 03 05:25:05 CET 2021 Alan Somers <asomers@FreeBSD.org> aio: micro-optimize the lio_opcode assignments
This allows slightly more efficient opcode testing in-kernel. It is
transparent to userland, except to applications that sneakily submit
aio fsync or aio mlock operations via lio_listio, which has never been
documented, requires the use of deliberately undefined constants
(LIO_SYNC and LIO_MLOCK), and is arguably a bug.
Reviewed by: jhb
Differential Revision: https://reviews.freebsd.org/D27942
|
| /freebsd/sys/kern/ |
| H A D | sys_socket.c | diff 2247f48941743cab420394b5ff0fc65ec8c69a99 Sun Jan 03 05:25:05 CET 2021 Alan Somers <asomers@FreeBSD.org> aio: micro-optimize the lio_opcode assignments
This allows slightly more efficient opcode testing in-kernel. It is
transparent to userland, except to applications that sneakily submit
aio fsync or aio mlock operations via lio_listio, which has never been
documented, requires the use of deliberately undefined constants
(LIO_SYNC and LIO_MLOCK), and is arguably a bug.
Reviewed by: jhb
Differential Revision: https://reviews.freebsd.org/D27942
|
| H A D | vfs_aio.c | diff 2247f48941743cab420394b5ff0fc65ec8c69a99 Sun Jan 03 05:25:05 CET 2021 Alan Somers <asomers@FreeBSD.org> aio: micro-optimize the lio_opcode assignments
This allows slightly more efficient opcode testing in-kernel. It is
transparent to userland, except to applications that sneakily submit
aio fsync or aio mlock operations via lio_listio, which has never been
documented, requires the use of deliberately undefined constants
(LIO_SYNC and LIO_MLOCK), and is arguably a bug.
Reviewed by: jhb
Differential Revision: https://reviews.freebsd.org/D27942
|