lio_listio - initiate a list of I/O requests
int lio_listio(int mode, struct aiocb *const aiocb_list,
int nitems, struct sigevent *sevp);
Link with -lrt.
() function initiates the list of I/O operations described
by the array aiocb_list
operation has one of the following values:
- The call blocks until all operations are complete. The sevp
argument is ignored.
- The I/O operations are queued for processing and the call returns
immediately. When all of the I/O operations complete, asynchronous
notification occurs, as specified by the sevp argument; see
sigevent(7) for details. If sevp is NULL, no asynchronous
argument is an array of pointers to aiocb
structures that describe I/O operations. These operations are executed in an
unspecified order. The nitems
argument specifies the size of the array
. null pointers in aiocb_list
In each control block in aiocb_list
, the aio_lio_opcode
specifies the I/O operation to be initiated, as follows:
- Initiate a read operation. The operation is queued as for a call to
aio_read(3) specifying this control block.
- Initiate a write operation. The operation is queued as for a call to
aio_write(3) specifying this control block.
- Ignore this control block.
The remaining fields in each control block have the same meanings as for
. The aio_sigevent
each control block can be used to specify notifications for the individual I/O
operations (see sigevent(7)
() returns 0 if all I/O
operations are successfully queued. Otherwise, -1 is returned, and
is set to indicate the error.
() returns 0 when all of the
I/O operations have completed successfully. Otherwise, -1 is returned, and
is set to indicate the error.
The return status from lio_listio
() provides information only about the
call itself, not about the individual I/O operations. One or more of the I/O
operations may fail, but this does not prevent other operations completing.
The status of individual I/O operations in aiocb_list
can be determined
. When an operation has completed, its return status
can be obtained using aio_return(3)
. Individual I/O operations can fail
for the reasons described in aio_read(3)
() function may fail for the following reasons:
- Out of resources.
- The number of I/O operations specified by nitems would cause the
limit AIO_MAX to be exceeded.
- mode is invalid, or nitems exceeds the limit
- mode was LIO_WAIT and a signal was caught before all I/O
operations completed. (This may even be one of the signals used for
asynchronous I/O completion notification.)
- One of more of the operations specified by aiocb_list failed. The
application can check the status of each operation using
() fails with the error EAGAIN
, then some of the operations in aiocb_list
may have been
initiated. If lio_listio
() fails for any other reason, then none of the
I/O operations has been initiated.
() function is available since glibc 2.1.
It is a good idea to zero out the control blocks before use. The control blocks
must not be changed while the I/O operations are in progress. The buffer areas
being read into or written from must not be accessed during the operations or
undefined results may occur. The memory areas involved must remain valid.
Simultaneous I/O operations specifying the same aiocb
This page is part of release 3.74 of the Linux man-pages
description of the project, information about reporting bugs, and the latest
version of this page, can be found at