NAME
aiowrite - asynchronous write SYNOPSIS
#include
int aiowrite(struct aiocb *aiocbp); Link with -lrt. DESCRIPTION The aiowrite() function queues the I/O request described by the buffer pointed to by aiocbp. This function is the asynchronous analog of write(2). The arguments of the call write(fd, buf, count) correspond (in order) to the fields aiofildes, aiobuf, and aionbytes of the structure pointed to by aiocbp. (See aio(7) for a description of the aiocb structure.) If OAPPEND is not set, the data is written starting at the absolute
file offset aiocbp->aiooffset, regardless of the current file offset. If OAPPEND is set, data is written at the end of the file in the same order as aiowrite() calls are made. After the call, the value of the current 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 aioerror(3). The return status of a completed I/O operation can be obtained aioreturn(3). Asynchronous notification of I/O completion can be obtained by setting
aiocbp->aiosigevent appropriately; see sigevent(7) for details. If POSIXPRIORITIZEDIO 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->aioreqprio.
The field aiocbp->aiolioopcode is ignored. No data is written to a regular file beyond its maximum offset. RETURN VALUE
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 aioreturn(3) (returns status -1) and aioerror(3) (error status—whatever one would have gotten in errno, such as EBADF). ERRORS EAGAIN Out of resources. EBADF aiofildes is not a valid file descriptor open for writing. EFBIG 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 this file. EINVAL One or more of aiooffset, aioreqprio, aionbytes are invalid. ENOSYS aiowrite() is not implemented. VERSIONS The aiowrite() function is available since glibc 2.1. ATTRIBUTES For an explanation of the terms used in this section, see attributes(7). ┌────────────┬───────────────┬─────────┐ │Interface │ Attribute │ Value │ ├────────────┼───────────────┼─────────┤
│aiowrite() │ Thread safety │ MT-Safe │ └────────────┴───────────────┴─────────┘ CONFORMING TO
POSIX.1-2001, POSIX.1-2008. NOTES It is a good idea to zero out the control block before use. The con‐ trol block must not be changed while the write operation is in progress. The buffer area being written out must not be accessed dur‐ ing the operation or undefined results may occur. The memory areas involved must remain valid. Simultaneous I/O operations specifying the same aiocb structure produce undefined results. SEE ALSO aiocancel(3), aioerror(3), aiofsync(3), aioread(3), aioreturn(3), aiosuspend(3), liolistio(3), aio(7) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
2012-05-08 AIOWRITE(3)