Manual Reference Pages - AIO_MLOCK (2)
aio_mlock struct aiocb *iocb
system call allows the calling process to lock into memory the
physical pages associated with the virtual address range starting at
The call returns immediately after the locking request has
been enqueued; the operation may or may not have completed at the time
the call returns.
pointer may be subsequently used as an argument to
in order to determine return or error status for the enqueued operation
while it is in progress.
If the request could not be enqueued (generally due to
then the call returns without having enqueued the request.
The Asynchronous I/O Control Block structure pointed to by
and the buffer that the
member of that structure references must remain valid until the
operation has completed.
For this reason, use of auto (stack) variables
for these objects is discouraged.
The asynchronous I/O control buffer
should be zeroed before the
call to avoid passing bogus context information to the kernel.
Modifications of the Asynchronous I/O Control Block structure or the
buffer contents after the request has been enqueued, but before the
request has completed, are not allowed.
.Rv -std aio_mlock
system call will fail if:
The request was not queued because of system resource limitations.
system call is not supported.
If the request is successfully enqueued, but subsequently cancelled
or an error occurs, the value returned by the
system call is per the
system call, and the value returned by the
system call is one of the error returns from the
system call, or
if the request was explicitly cancelled via a call to
system call is a
extension, and should not be used in portable code.
system call first appeared in
.Fx 10.0 .
The system call was introduced by
.An Gleb Smirnoff Aq glebius@FreeBSD.org .
Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.