AIO_WRITE(3) Library Functions Manual AIO_WRITE(3)

aio_write — asynchronous write to a file (REALTIME)


#include <aio.h>

int aio_write(struct aiocb *aiocbp);

The aio_write () function shall write aiocbp -> to the file associated with aiocbp -> aio_fildes from the buffer pointed to by aiocbp -> aio_buf. The function shall return when the write request has been initiated or, at a minimum, queued to the file or device.

If prioritized I/O is supported for this file, then the asynchronous operation shall be submitted at a priority equal to the scheduling priority of the process minus aiocbp -> .

The aiocbp argument may be used as an argument to aio_error(3) and aio_return(3) in order to determine the error status and return status, respectively, of the asynchronous operation while it is proceeding.

The aiocbp argument points to an structure. If the buffer pointed to by aiocbp -> aio_buf or the control block pointed to by aiocbp becomes an illegal address prior to asynchronous I/O completion, then the behavior is undefined.

If O_APPEND is not set for the file descriptor aio_fildes, then the requested operation shall take place at the absolute position in the file as given by aio_offset, as if lseek(3) were called immediately prior to the operation with an equal to aio_offset and a equal to SEEK_SET. If O_APPEND is set for the file descriptor, write operations append to the file in the same order as the calls were made. After a successful call to enqueue an asynchronous I/O operation, the value of the file offset for the file is unspecified.

The aiocbp -> field shall be ignored by aio_write ().

Simultaneous asynchronous operations using the same aiocbp produce undefined results.

If synchronized I/O is enabled on the file associated with aiocbp -> aio_fildes, the behavior of this function shall be according to the definitions of synchronized I/O data integrity completion, and synchronized I/O file integrity completion.

For any system action that changes the process memory space while an asynchronous I/O is outstanding to the address range being changed, the result of that action is undefined.

For regular files, no data transfer shall occur past the offset maximum established in the open file description associated with aiocbp -> aio_fildes.

The aio_write () function shall return the value zero to the calling process if the I/O operation is successfully queued; otherwise, the function shall return the value -1 and set errno to indicate the error.

The aio_write () function shall fail if:

The requested asynchronous I/O operation was not queued due to system resource limitations.

Each of the following conditions may be detected synchronously at the time of the call to aio_write (), or asynchronously. If any of the conditions below are detected synchronously, the aio_write () function shall return -1 and set errno to the corresponding value. If any of the conditions below are detected asynchronously, the return status of the asynchronous operation shall be set to -1, and the error status of the asynchronous operation is set to the corresponding value.

The aiocbp -> aio_fildes argument is not a valid file descriptor open for writing.
The file offset value implied by aiocbp -> aio_offset would be invalid, aiocbp -> aio_reqprio is not a valid value, or aiocbp -> aio_nbytes is an invalid value.

In the case that the aio_write () successfully queues the I/O operation, the return status of the asynchronous operation shall be one of the values normally returned by the write(3) function call. If the operation is successfully queued but is subsequently canceled or encounters an error, the error status for the asynchronous operation contains one of the values normally set by the write(3) function call, or one of the following:

The aiocbp -> aio_fildes argument is not a valid file descriptor open for writing.
The file offset value implied by aiocbp -> aio_offset would be invalid.
The requested I/O was canceled before the I/O completed due to an explicit () request.

The following condition may be detected synchronously or asynchronously:

The file is a regular file, aiobcp -> aio_nbytes is greater than 0, and the starting offset in aiobcp -> aio_offset is at or beyond the offset maximum in the open file description associated with aiocbp -> aio_fildes .

None.

The aio_write () function is part of the Asynchronous Input and Output option and need not be available on all implementations.

None.

None.

aio_cancel(3) , aio_error(3) , aio_read(3) , aio_return(3) , close(3) , exec(3) , exit(3) , fork(3) , lio_listio(3) , lseek(3) , write(3) , the Base Definitions volume of IEEE Std 1003.1-2001 (“POSIX.1”), <aio.h>

First released in Issue 5. Included for alignment with the POSIX Realtime Extension.

Large File Summit extensions are added.

The [ENOSYS] error condition has been removed as stubs need not be provided if an implementation does not support the Asynchronous Input and Output option.

The APPLICATION USAGE section is added.

The following new requirements on POSIX implementations derive from alignment with the Single UNIX Specification:

  • In the DESCRIPTION, text is added to indicate that for regular files no data transfer occurs past the offset maximum established in the open file description associated with aiocbp -> aio_fildes.
  • The [EFBIG] error is added as part of the large file support extensions.

footer end

December 6, 2001 posix.fail