From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCH liburing 1/1] man/io_uring_enter.2: notes about cqe-skip & drain interoperability
Date: Wed, 1 Dec 2021 13:20:37 +0000 [thread overview]
Message-ID: <8c81bf9b01a54d1214bb65678c2ff1362a9f9328.1638364791.git.asml.silence@gmail.com> (raw)
IOSQE_CQE_SKIP_SUCCESS can't be used together with draining in a single
ring, add a paragraph explaining what are the restrictions.
Signed-off-by: Pavel Begunkov <[email protected]>
---
man/io_uring_enter.2 | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/man/io_uring_enter.2 b/man/io_uring_enter.2
index b003e05..871cbce 100644
--- a/man/io_uring_enter.2
+++ b/man/io_uring_enter.2
@@ -1115,6 +1115,15 @@ CQEs in cases where the side effects of a successfully executed operation is
enough for userspace to know the state of the system. One such example would
be writing to a synchronisation file.
+It also doesn't work with
+.B IOSQE_IO_DRAIN.
+Using both of them in a ring is undefined behaviour even when they never appear
+together in a single request. Currently, after first request with
+.B IOSQE_CQE_SKIP_SUCCESS,
+all subsequent requests marked for drain will be failed. However, the
+error reporting is best effort only and restrictions may change in
+the future.
+
Available since 5.17.
.PP
--
2.34.0
next reply other threads:[~2021-12-01 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 13:20 Pavel Begunkov [this message]
2021-12-07 16:18 ` [PATCH liburing 1/1] man/io_uring_enter.2: notes about cqe-skip & drain interoperability Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8c81bf9b01a54d1214bb65678c2ff1362a9f9328.1638364791.git.asml.silence@gmail.com \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox