summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2021-03-04 17:20:31 -0700
committerJens Axboe <axboe@kernel.dk>2021-03-04 17:20:31 -0700
commit35c199c48dfd54ad46b96e386882e7ac341314c5 (patch)
treefc69e843441db84344c86d1b76eeb7e454885a68
parentb013dfd5a5f65116373d5e0f0bdfb73db9d8816e (diff)
downloadliburing-35c199c48dfd54ad46b96e386882e7ac341314c5.tar.gz
liburing-35c199c48dfd54ad46b96e386882e7ac341314c5.tar.bz2
man/io_uring_enter.2: note that -EBUSY can also happen for getevents
If we try and wait for events AND the ring is in overflow condition to the extent that it cannot be flushed, then waiting for more is nonsensical. The kernel will return -EBUSY for that condition as well. Signed-off-by: Jens Axboe <axboe@kernel.dk>
-rw-r--r--man/io_uring_enter.23
1 files changed, 2 insertions, 1 deletions
diff --git a/man/io_uring_enter.2 b/man/io_uring_enter.2
index 086207d..f898ffd 100644
--- a/man/io_uring_enter.2
+++ b/man/io_uring_enter.2
@@ -976,7 +976,8 @@ for details on how to enable the ring.
The application is attempting to overcommit the number of requests it can have
pending. The application should wait for some completions and try again. May
occur if the application tries to queue more requests than we have room for in
-the CQ ring.
+the CQ ring, or if the application attempts to wait for more events without
+having reaped the ones already present in the CQ ring.
.TP
.B EINVAL
Some bits in the