io_uring_setup.2: formatting and addition of read/write fixed

Signed-off-by: Jens Axboe <axboe@kernel.dk>

1 files changed, 15 insertions, 11 deletions

diff --git a/man/io_uring_setup.2 b/man/io_uring_setup.2
index dc0b5f2..27cf864 100644
--- a/man/io_uring_setup.2
+++ b/man/io_uring_setup.2
@@ -176,21 +176,25 @@ If this flag is set, applications can be certain that any data for
 async offload has been consumed when the kernel has consumed the SQE.
 .TP
 .B IORING_FEAT_RW_CUR_POS
-If this flag is set, applications can specify offset == -1 with
-.B IORING_OP_READV,
-.B IORING_OP_WRITEV,
-.B IORING_OP_READ,
-and
-.B IORING_OP_WRITE
+If this flag is set, applications can specify
+.I offset
+== -1 with
+.B IORING_OP_{READV,WRITEV}
+,
+.B IORING_OP_{READ,WRITE}_FIXED
+, and
+.B IORING_OP_{READ,WRITE}
 to mean current file position, which behaves like
 .I preadv2(2)
 and
 .I pwritev2(2)
-with offset == -1. It'll use (and update) the current
-file position. This obviously comes with the caveat that if the
-application has multiple read/writes in flight, then the end result
-will not be as expected. This is similar to threads sharing a file
-descriptor and doing IO using the current file position.
+with
+.I offset
+== -1. It'll use (and update) the current file position. This obviously comes
+with the caveat that if the application has multiple reads or writes in flight,
+then the end result will not be as expected. This is similar to threads sharing
+a file descriptor and doing IO using the current file position.
+
 .PP
 The rest of the fields in the
 .I struct io_uring_params