aio_fsync(2) [freebsd man page]

AIO_FSYNC(2)						      BSD System Calls Manual						      AIO_FSYNC(2)

NAME

     aio_fsync -- asynchronous file synchronization (REALTIME)

LIBRARY

     Standard C Library (libc, -lc)

SYNOPSIS

     #include <aio.h>

     int
     aio_fsync(int op, struct aiocb *iocb);

DESCRIPTION

     The aio_fsync() system call allows the calling process to move all modified data associated with the descriptor iocb->aio_fildes to a perma-
     nent storage device.  The call returns immediately after the synchronization request has been enqueued to the descriptor; the synchronization
     may or may not have completed at the time the call returns.

     The op argument can only be set to O_SYNC to cause all currently queued I/O operations to be completed as if by a call to fsync(2).

     If _POSIX_PRIORITIZED_IO is defined, and the descriptor supports it, then the enqueued operation is submitted at a priority equal to that of
     the calling process minus iocb->aio_reqprio.

     The iocb pointer may be subsequently used as an argument to aio_return() and aio_error() 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 invalid arguments), the call returns without having enqueued the request.

RETURN VALUES

     The aio_fsync() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indi-
     cate the error.

ERRORS

     The aio_fsync() system call will fail if:

     [EAGAIN]		The request was not queued because of system resource limitations.

     [ENOSYS]		The aio_fsync() system call is not supported.

     [EINVAL]		A value of the op argument is not set to O_SYNC.

     The following conditions may be synchronously detected when the aio_fsync() system call is made, or asynchronously, at any time thereafter.
     If they are detected at call time, aio_fsync() returns -1 and sets errno appropriately; otherwise the aio_return() system call must be
     called, and will return -1, and aio_error() must be called to determine the actual value that would have been returned in errno.

     [EBADF]		The iocb->aio_fildes argument is not a valid descriptor.

     [EINVAL]		This implementation does not support synchronized I/O for this file.

     If the request is successfully enqueued, but subsequently cancelled or an error occurs, the value returned by the aio_return() system call is
     per the read(2) and write(2) system calls, and the value returned by the aio_error() system call is one of the error returns from the read(2)
     or write(2) system calls.

SEE ALSO

     aio_cancel(2), aio_error(2), aio_read(2), aio_return(2), aio_suspend(2), aio_waitcomplete(2), aio_write(2), fsync(2), siginfo(3), aio(4)

STANDARDS

     The aio_fsync() system call is expected to conform to the IEEE Std 1003.1 (``POSIX.1'') standard.

HISTORY

     The aio_fsync() system call first appeared in FreeBSD 7.0.

BSD
								 December 27, 2013							       BSD

Check Out this Related Man Page

AIO_MLOCK(2)						      BSD System Calls Manual						      AIO_MLOCK(2)

NAME

     aio_mlock -- asynchronous mlock(2) operation

LIBRARY

     Standard C Library (libc, -lc)

SYNOPSIS

     #include <aio.h>

     int
     aio_mlock(struct aiocb *iocb);

DESCRIPTION

     The aio_mlock() system call allows the calling process to lock into memory the physical pages associated with the virtual address range
     starting at iocb->aio_buf for iocb->aio_nbytes bytes.  The call returns immediately after the locking request has been enqueued; the opera-
     tion may or may not have completed at the time the call returns.

     The iocb pointer may be subsequently used as an argument to aio_return() and aio_error() 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 aio(4) limits), then the call returns without having enqueued the request.

RESTRICTIONS

     The Asynchronous I/O Control Block structure pointed to by iocb and the buffer that the iocb->aio_buf 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 iocb should be zeroed before the aio_mlock() call to avoid passing bogus context information to the ker-
     nel.

     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.

RETURN VALUES

     The aio_mlock() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indi-
     cate the error.

ERRORS

     The aio_mlock() system call will fail if:

     [EAGAIN]		The request was not queued because of system resource limitations.

     [ENOSYS]		The aio_mlock() system call is not supported.

     If the request is successfully enqueued, but subsequently cancelled or an error occurs, the value returned by the aio_return() system call is
     per the mlock(2) system call, and the value returned by the aio_error() system call is one of the error returns from the mlock(2) system
     call, or ECANCELED if the request was explicitly cancelled via a call to aio_cancel().

SEE ALSO

     aio_cancel(2), aio_error(2), aio_return(2), mlock(2), aio(4)

PORTABILITY

     The aio_mlock() system call is a FreeBSD extension, and should not be used in portable code.

HISTORY

     The aio_mlock() system call first appeared in FreeBSD 10.0.

AUTHORS

     The system call was introduced by Gleb Smirnoff <glebius@FreeBSD.org>.

BSD
								   June 3, 2013 							       BSD

Linux and UNIX Man Pages

aio_fsync(2) [freebsd man page]

Check Out this Related Man Page