aio_write - asynchronous write
int aio_write(struct aiocb *aiocbp);
Link with -lrt
() function queues the I/O request described by the buffer
pointed to by aiocbp
. This function is the asynchronous analog of
. The arguments of the call
write(fd, buf, count)
correspond (in order) to the fields aio_fildes
of the structure pointed to by aiocbp
for a description of the aiocb
is not set, the data is written starting at the absolute
, regardless of the file offset. If
is set, data is written at the end of the file in the same
order as aio_write
() calls are made. After the call, the value of the
file offset is unspecified.
The "asynchronous" means that this call returns as soon as the request
has been enqueued; the write may or may not have completed when the call
returns. One tests for completion using aio_error(3)
. The return status
of a completed I/O operation can be obtained aio_return(3)
Asynchronous notification of I/O completion can be obtained by setting
appropriately; see sigevent(7)
is defined, and this file supports it, then the
asynchronous operation is submitted at a priority equal to that of the calling
process minus aiocbp->aio_reqprio
The field aiocbp->aio_lio_opcode
No data is written to a regular file beyond its maximum offset.
On success, 0 is returned. On error, the request is not enqueued, -1 is
returned, and errno
is set appropriately. If an error is detected only
later, it will be reported via aio_return(3)
(returns status -1) and
(error status—whatever one would have gotten in
, such as EBADF
- Out of resources.
- aio_fildes is not a valid file descriptor open for
- The file is a regular file, we want to write at least one
byte, but the starting position is at or beyond the maximum offset for
- One or more of aio_offset, aio_reqprio,
aio_nbytes are invalid.
- aio_write() is not implemented.
() function is available since glibc 2.1.
For an explanation of the terms used in this section, see attributes(7)
It is a good idea to zero out the control block before use. The control block
must not be changed while the write operation is in progress. The buffer area
being written out must not be accessed during the operation 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 4.16 of the Linux man-pages
description of the project, information about reporting bugs, and the latest
version of this page, can be found at