From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH liburing 1/1] man/io_uring_setup.2: document IORING_SETUP_SINGLE_ISSUER
Date: Fri, 22 Jul 2022 12:49:02 +0100 [thread overview]
Message-ID: <9e282a50456df4451e28189bd3ac6e54d598ecc3.1658490521.git.asml.silence@gmail.com> (raw)
Signed-off-by: Pavel Begunkov <[email protected]>
---
man/io_uring_setup.2 | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/man/io_uring_setup.2 b/man/io_uring_setup.2
index 75c69ff..0f57d8f 100644
--- a/man/io_uring_setup.2
+++ b/man/io_uring_setup.2
@@ -239,6 +239,24 @@ variant. This is a requirement for using certain request types, as of 5.19
only the
.B IORING_OP_URING_CMD
passthrough command for NVMe passthrough needs this. Available since 5.19.
+.TP
+.B IORING_SETUP_SINGLE_ISSUER
+A hint to the kernel that only a single task can submit requests, which is used
+for internal optimisations. The kernel enforces the rule, which only affects
+.I
+io_uring_enter(2)
+calls submitting requests and will fail them with
+.B -EEXIST
+if the restriction is violated.
+The submitter task may differ from the task that created the ring.
+Note that when
+.B IORING_SETUP_SQPOLL
+is set it is considered that the polling task is doing all submissions
+on behalf of the userspace and so it always complies with the rule disregarding
+how many userspace tasks do
+.I
+io_uring_enter(2).
+Available since 5.20.
.PP
If no flags are specified, the io_uring instance is setup for
interrupt driven I/O. I/O may be submitted using
--
2.37.0
next reply other threads:[~2022-07-22 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 11:49 Pavel Begunkov [this message]
2022-07-22 15:21 ` [PATCH liburing 1/1] man/io_uring_setup.2: document IORING_SETUP_SINGLE_ISSUER 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=9e282a50456df4451e28189bd3ac6e54d598ecc3.1658490521.git.asml.silence@gmail.com \
[email protected] \
[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