man: clarify non-seekable file read/write API

* The io_uring_enter and io_uring_prep_* pages seem to contradict each
  other.
* I'd like for -1 offsets to explicitly be supported for non-seekable
  files.

Fixes: https://github.com/axboe/liburing/issues/642
Signed-off-by: Frederick Mayle <fmayle@google.com>
This commit is contained in:
Frederick Mayle
2022-09-30 00:23:19 +00:00
parent 5731813a08
commit 5b08ddeb22
7 changed files with 8 additions and 8 deletions
+2 -2
View File
@@ -253,7 +253,7 @@ and
.BR pwritev2 (2).
If the file is not seekable,
.I off
must be set to zero.
must be set to zero or -1.
.TP
.B IORING_OP_READ_FIXED
@@ -789,7 +789,7 @@ contains the read or write offset. If
.I fd
does not refer to a seekable file,
.I off
must be set to zero. If
must be set to zero or -1. If
.I offs
is set to
.B -1
+1 -1
View File
@@ -40,7 +40,7 @@ current file offset may result in unpredictable behavior, unless access
to the file is serialized. It is not encouraged to use this feature, if it's
possible to provide the desired IO offset from the application or library.
On files that are not capable of seeking, the offset is ignored.
On files that are not capable of seeking, the offset must be 0 or -1.
After the read has been prepared it can be submitted with one of the submit
functions.
+1 -1
View File
@@ -41,7 +41,7 @@ current file offset may result in unpredictable behavior, unless access
to the file is serialized. It is not encouraged to use this feature, if it's
possible to provide the desired IO offset from the application or library.
On files that are not capable of seeking, the offset is ignored.
On files that are not capable of seeking, the offset must be 0 or -1.
After the write has been prepared it can be submitted with one of the submit
functions.
+1 -1
View File
@@ -67,7 +67,7 @@ current file offset may result in unpredictable behavior, unless access
to the file is serialized. It is not encouraged to use this feature, if it's
possible to provide the desired IO offset from the application or library.
On files that are not capable of seeking, the offset is ignored.
On files that are not capable of seeking, the offset must be 0 or -1.
After the write has been prepared, it can be submitted with one of the submit
functions.
+1 -1
View File
@@ -40,7 +40,7 @@ current file offset may result in unpredictable behavior, unless access
to the file is serialized. It is not encouraged to use this feature if it's
possible to provide the desired IO offset from the application or library.
On files that are not capable of seeking, the offset is ignored.
On files that are not capable of seeking, the offset must be 0 or -1.
After the write has been prepared, it can be submitted with one of the submit
functions.
+1 -1
View File
@@ -41,7 +41,7 @@ current file offset may result in unpredictable behavior, unless access
to the file is serialized. It is not encouraged to use this feature if it's
possible to provide the desired IO offset from the application or library.
On files that are not capable of seeking, the offset is ignored.
On files that are not capable of seeking, the offset must be 0 or -1.
After the write has been prepared it can be submitted with one of the submit
functions.
+1 -1
View File
@@ -67,7 +67,7 @@ current file offset may result in unpredictable behavior, unless access
to the file is serialized. It is not encouraged to use this feature if it's
possible to provide the desired IO offset from the application or library.
On files that are not capable of seeking, the offset is ignored.
On files that are not capable of seeking, the offset must be 0 or -1.
After the write has been prepared, it can be submitted with one of the submit
functions.