man/io_uring_enter.2: improve timeout documentation

- Missing mention of -ENOENT on timeout removal
- Mention the clock source used is CLOCK_MONOTONIC

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

1 files changed, 9 insertions, 2 deletions

diff --git a/man/io_uring_enter.2 b/man/io_uring_enter.2
index c5b3a3f..12fadf0 100644
--- a/man/io_uring_enter.2
+++ b/man/io_uring_enter.2
@@ -251,7 +251,9 @@ may contain a completion event count. If not set, this defaults to 1. A timeout
 will trigger a wakeup event on the completion ring for anyone waiting for
 events. A timeout condition is met when either the specified timeout expires,
 or the specified number of events have completed. Either condition will
-trigger the event. The request will complete with
+trigger the event. io_uring timeouts use the
+.B CLOCK_MONOTONIC
+clock source. The request will complete with
 .I -ETIME
 if the timeout got completed through expiration of the timer, or
 .I 0
@@ -274,6 +276,7 @@ this request will terminate with a result value of
 .I -EBUSY
 If the timeout request wasn't found, the request will terminate with a result
 value of
+.I -ENOENT
 
 .TP
 .B IORING_OP_ACCEPT
@@ -323,7 +326,11 @@ complete with
 .I -ETIME
 if the timer expired and the linked request was attempted cancelled, or
 .I -ECANCELED
-if the timer got cancelled because of completion of the linked request.
+if the timer got cancelled because of completion of the linked request. Like
+.B IORING_OP_TIMEOUT
+the clock source used is
+.B CLOCK_MONOTONIC
+
 
 .TP
 .B IORING_OP_CONNECT