From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH v2 0/4] allow to skip CQE posting
Date: Wed, 10 Nov 2021 15:49:30 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
It's expensive enough to post an CQE, and there are other
reasons to want to ignore them, e.g. for link handling and
it may just be more convenient for the userspace.
Try to cover most of the use cases with one flag. The overhead
is one "if (cqe->flags & IOSQE_CQE_SKIP_SUCCESS)" check per
requests and a bit bloated req_set_fail(), should be bearable.
See 2/4 for the actual description of the flag.
v2: don't allow drain with the new flag (see 4/4)
add IORING_FEAT_CQE_SKIP
Pavel Begunkov (4):
io_uring: clean cqe filling functions
io_uring: add option to skip CQE posting
io_uring: don't spinlock when not posting CQEs
io_uring: disable drain with cqe skip
fs/io_uring.c | 114 +++++++++++++++++++++++-----------
include/uapi/linux/io_uring.h | 4 ++
2 files changed, 81 insertions(+), 37 deletions(-)
--
2.33.1
next reply other threads:[~2021-11-10 15:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 15:49 Pavel Begunkov [this message]
2021-11-10 15:49 ` [PATCH v2 1/4] io_uring: clean cqe filling functions Pavel Begunkov
2021-11-10 15:49 ` [PATCH v2 2/4] io_uring: add option to skip CQE posting Pavel Begunkov
2021-11-10 15:49 ` [PATCH v2 3/4] io_uring: don't spinlock when not posting CQEs Pavel Begunkov
2021-11-25 3:48 ` Hao Xu
2021-11-25 7:35 ` Hao Xu
2021-11-10 15:49 ` [PATCH v2 4/4] io_uring: disable drain with cqe skip Pavel Begunkov
2021-11-10 16:14 ` [PATCH v2 0/4] allow to skip CQE posting Jens Axboe
2021-11-10 16:42 ` Pavel Begunkov
2021-11-10 16:47 ` Jens Axboe
2021-11-24 17:55 ` Pavel Begunkov
2021-11-24 17:57 ` Jens Axboe
2021-11-24 18:02 ` Pavel Begunkov
2021-11-24 18:17 ` Jens Axboe
2021-11-25 9:35 ` Hao Xu
2021-11-25 14:22 ` Pavel Begunkov
2021-11-24 18:18 ` Jens Axboe
2021-12-06 19:49 ` Olivier Langlois
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 \
[email protected] \
[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