summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2019-12-25 21:42:57 -0700
committerJens Axboe <axboe@kernel.dk>2019-12-25 21:42:57 -0700
commit9d65469834ee5991c99575854f356815b8a241ec (patch)
tree756c6844fc36172ce16a8029b44a8811159a74a2 /man
parent93eccf82a908ceb13061d95807b8f119d50b1b90 (diff)
downloadliburing-9d65469834ee5991c99575854f356815b8a241ec.tar.gz
liburing-9d65469834ee5991c99575854f356815b8a241ec.tar.bz2
io_uring_setup.2: minor clarification
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'man')
-rw-r--r--man/io_uring_setup.24
1 files changed, 2 insertions, 2 deletions
diff --git a/man/io_uring_setup.2 b/man/io_uring_setup.2
index 4245579..dc0b5f2 100644
--- a/man/io_uring_setup.2
+++ b/man/io_uring_setup.2
@@ -182,11 +182,11 @@ If this flag is set, applications can specify offset == -1 with
.B IORING_OP_READ,
and
.B IORING_OP_WRITE
-to mean file position, which behaves like
+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
+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