|LIO_LISTIO(2)||System Calls Manual||LIO_LISTIO(2)|
LIBRARY¶Standard C Library (libc, -lc)
struct aiocb * const list, int
nent, struct sigevent *sig);
lio_listio() function initiates a list of I/O requests with a single function call. The list argument is an array of pointers to aiocb structures describing each operation to perform, with nent elements.
NULLelements are ignored.
The aio_lio_opcode field of each aiocb specifies the operation to be performed. The following operations are supported:
- Read data as if by a call to aio_read(2).
- No operation.
- Write data as if by a call to aio_write(2).
If the mode argument is
not return until all the requested operations have been completed. If
sig can be used to request asynchronous notification
when all operations have completed. If sig is
NULL, no notification is sent.
SIGEV_KEVENT notifications, the posted
kevent will contain:
|udata||value stored in sig->sigev_value|
SIGEV_THREAD_ID notifications, the information for
the queued signal will include
SI_ASYNCIO in the
si_code field and the value stored in
sig->sigev_value in the
SIGEV_THREAD notifications, the value
stored in sig->sigev_value is passed to the
sig->sigev_notify_function as described in
The order in which the requests are carried out is not specified; in particular, there is no guarantee that they will be executed in the order 0, 1, ..., nent-1.
RETURN VALUES¶If mode is
lio_listio() function returns 0 if the operations completed successfully, otherwise -1.
If mode is
function returns 0 if the operations are successfully queued, otherwise
lio_listio() function will fail if:
- There are not enough resources to enqueue the requests.
- The request would cause the system-wide limit
AIO_MAXto be exceeded.
- The mode argument is neither
LIO_NOWAIT, or nent is greater than
- The asynchronous notification method in sig->sigev_notify is invalid or not supported.
- A signal interrupted the system call before it could be completed.
- One or more requests failed.
lio_listio() succeeds, or fails with an
error code of
EIO, some of the requests may have been
initiated. The caller should check the error status of each
aiocb structure individually by calling
SEE ALSO¶aio_error(2), aio_read(2), aio_write(2), read(2), write(2), sigevent(3), siginfo(3), aio(4)
lio_listio() function is expected to conform to IEEE Std 1003.1-2001 (“POSIX.1”).
|July 15, 2016||Linux 4.9.0-9-amd64|