PROLOG<\/a> This manual page is part of the POSIX Programmer\u2019s Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.<\/p>\n lio_listio \u2014 list directed I\/O<\/p>\n #include int lio_listio(int mode<\/i>, struct aiocb *restrict const list<\/i>[restrict], The lio_listio<\/i>() function shall initiate a list of I\/O requests with a single function call.<\/p>\n The mode<\/i> argument takes one of the values LIO_WAIT or LIO_NOWAIT declared in If the mode<\/i> argument is LIO_NOWAIT, the function shall return immediately, and asynchronous notification shall occur, according to the sig<\/i> argument, when all the I\/O operations complete. If sig<\/i> is NULL, then no asynchronous notification shall occur. If sig<\/i> is not NULL, asynchronous notification occurs as specified in Section 2.4.1<\/i>, Signal Generation and Delivery<\/i> when all the requests in list<\/i> have completed.<\/p>\n The I\/O requests enumerated by list<\/i> are submitted in an unspecified order.<\/p>\n The list<\/i> argument is an array of pointers to aiocb<\/b> structures. The array contains nent<\/i> elements. The array may contain NULL elements, which shall be ignored.<\/p>\n If the buffer pointed to by list<\/i> or the aiocb<\/b> structures pointed to by the elements of the array list<\/i> become illegal addresses before all asynchronous I\/O completed and, if necessary, the notification is sent, then the behavior is undefined. If the buffers pointed to by the aio_buf<\/i> member of the aiocb<\/b> structure pointed to by the elements of the array list<\/i> become illegal addresses prior to the asynchronous I\/O associated with that aiocb<\/b> structure being completed, the behavior is undefined.<\/p>\n The aio_lio_opcode<\/i> field of each aiocb<\/b> structure specifies the operation to be performed. The supported operations are LIO_READ, LIO_WRITE, and LIO_NOP; these symbols are defined in The aio_fildes<\/i> member specifies the file descriptor on which the operation is to be performed.<\/p>\n The aio_buf<\/i> member specifies the address of the buffer to or from which the data is transferred.<\/p>\n The aio_nbytes<\/i> member specifies the number of bytes of data to be transferred.<\/p>\n The members of the aiocb<\/b> structure further describe the I\/O operation to be performed, in a manner identical to that of the corresponding aiocb<\/b> structure when used by the aio_read<\/i>() and aio_write<\/i>() functions.<\/p>\n The nent<\/i> argument specifies how many elements are members of the list; that is, the length of the array.<\/p>\n The behavior of this function is altered according to the definitions of synchronized I\/O data integrity completion and synchronized I\/O file integrity completion if synchronized I\/O is enabled on the file associated with aio_fildes<\/i>.<\/p>\n For regular files, no data transfer shall occur past the offset maximum established in the open file description associated with aiocbp<\/i>\u2212>aio_fildes<\/i>.<\/p>\n If sig<\/i>\u2212>sigev_notify<\/i> is SIGEV_THREAD and sig<\/i>\u2212>sigev_notify_attributes<\/i> is a non-null pointer and the block pointed to by this pointer becomes an illegal address prior to all asynchronous I\/O being completed, then the behavior is undefined.<\/p>\n If the mode<\/i> argument has the value LIO_NOWAIT, the lio_listio<\/i>() function shall return the value zero if the I\/O operations are successfully queued; otherwise, the function shall return the value \u22121 and set errno<\/i> to indicate the error.<\/p>\n If the mode<\/i> argument has the value LIO_WAIT, the lio_listio<\/i>() function shall return the value zero when all the indicated I\/O has completed successfully. Otherwise, lio_listio<\/i>() shall return a value of \u22121 and set errno<\/i> to indicate the error.<\/p>\n In either case, the return value only indicates the success or failure of the lio_listio<\/i>() call itself, not the status of the individual I\/O requests. In some cases one or more of the I\/O requests contained in the list may fail. Failure of an individual request does not prevent completion of any other individual request. To determine the outcome of each I\/O request, the application shall examine the error status associated with each aiocb<\/b> control block. The error statuses so returned are identical to those returned as the result of an aio_read<\/i>() or aio_write<\/i>() function.<\/p>\n The lio_listio<\/i>() function shall fail if:<\/p>\n
NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
RETURN VALUE<\/a>
ERRORS<\/a>
EXAMPLES<\/a>
APPLICATION USAGE<\/a>
RATIONALE<\/a>
FUTURE DIRECTIONS<\/a>
SEE ALSO<\/a>
COPYRIGHT<\/a> <\/p>\n
\nPROLOG <\/a> <\/h2>\n
NAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
int nent<\/i>, struct sigevent *restrict sig<\/i>);<\/p>\nDESCRIPTION <\/a> <\/h2>\n
RETURN VALUE <\/a> <\/h2>\n
ERRORS <\/a> <\/h2>\n