aio_write — asynchronous write
||struct aiocb *aiocbp
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
write(fd, buf, count)
correspond (in order) to the fields
aio_nbytes of the structure pointed to by
aio(7) for a description of
the aiocb structure.)
O_APPEND is not set, the
data is written starting at the absolute position
regardless of the file offset. If
O_APPEND 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) for
defined, and this file supports it, then the asynchronous
operation is submitted at a priority equal to that of the
calling process minus
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 aio_error(3) (error
status—whatever one would have gotten in
errno, such as EBADF).
Out of resources.
aio_fildes is not a
valid file descriptor open for writing.
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.
One or more of
aio_nbytes are invalid.
aio_write() is not
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 structure produce undefined results.
This page is part of release 4.07 of the Linux
man-pages project. A
description of the project, information about reporting bugs,
and the latest version of this page, can be found at
Copyright (c) 2003 Andries Brouwer (aebcwi.nl)
This is free documentation; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of
the License, or (at your option) any later version.
The GNU General Public License's references to "object code"
and "executables" are to be interpreted as the output of any
document formatting or typesetting system, including
intermediate and printed output.
This manual is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public
License along with this manual; if not, see