diff options
Diffstat (limited to 'man3/lio_listio.3')
-rw-r--r-- | man3/lio_listio.3 | 40 |
1 files changed, 20 insertions, 20 deletions
diff --git a/man3/lio_listio.3 b/man3/lio_listio.3 index bd9367d7c..9e634fd16 100644 --- a/man3/lio_listio.3 +++ b/man3/lio_listio.3 @@ -39,7 +39,7 @@ When all of the I/O operations complete, asynchronous notification occurs, as specified by the .I sevp argument; see -.BR sigevent (3type) +.MR sigevent 3type for details. If .I sevp @@ -68,27 +68,27 @@ field specifies the I/O operation to be initiated, as follows: .B LIO_READ Initiate a read operation. The operation is queued as for a call to -.BR aio_read (3) +.MR aio_read 3 specifying this control block. .TP .B LIO_WRITE Initiate a write operation. The operation is queued as for a call to -.BR aio_write (3) +.MR aio_write 3 specifying this control block. .TP .B LIO_NOP Ignore this control block. .P The remaining fields in each control block have the same meanings as for -.BR aio_read (3) +.MR aio_read 3 and -.BR aio_write (3). +.MR aio_write 3 . The .I aio_sigevent fields of each control block can be used to specify notifications for the individual I/O operations (see -.BR sigevent (7)). +.MR sigevent 7 ). .SH RETURN VALUE If .I mode @@ -119,14 +119,14 @@ but this does not prevent other operations completing. The status of individual I/O operations in .I aiocb_list can be determined using -.BR aio_error (3). +.MR aio_error 3 . When an operation has completed, its return status can be obtained using -.BR aio_return (3). +.MR aio_return 3 . Individual I/O operations can fail for the reasons described in -.BR aio_read (3) +.MR aio_read 3 and -.BR aio_write (3). +.MR aio_write 3 . .SH ERRORS The .BR lio_listio () @@ -149,7 +149,7 @@ was .B LIO_WAIT and a signal was caught before all I/O operations completed; see -.BR signal (7). +.MR signal 7 . (This may even be one of the signals used for asynchronous I/O completion notification.) .TP @@ -167,7 +167,7 @@ One of more of the operations specified by failed. .\" e.g., ioa_reqprio or aio_lio_opcode was invalid The application can check the status of each operation using -.BR aio_return (3). +.MR aio_return 3 . .P If .BR lio_listio () @@ -185,7 +185,7 @@ fails for any other reason, then none of the I/O operations has been initiated. .SH ATTRIBUTES For an explanation of the terms used in this section, see -.BR attributes (7). +.MR attributes 7 . .TS allbox; lbx lb lb @@ -215,10 +215,10 @@ Simultaneous I/O operations specifying the same .I aiocb structure produce undefined results. .SH SEE ALSO -.BR aio_cancel (3), -.BR aio_error (3), -.BR aio_fsync (3), -.BR aio_return (3), -.BR aio_suspend (3), -.BR aio_write (3), -.BR aio (7) +.MR aio_cancel 3 , +.MR aio_error 3 , +.MR aio_fsync 3 , +.MR aio_return 3 , +.MR aio_suspend 3 , +.MR aio_write 3 , +.MR aio 7 |