From: Pavel Begunkov <asml.silence@gmail.com>
To: Usama Arif <usama.arif@bytedance.com>,
io-uring@vger.kernel.org, axboe@kernel.dk,
linux-kernel@vger.kernel.org
Cc: fam.zheng@bytedance.com
Subject: Re: [PATCH 1/2] io_uring: avoid ring quiesce while registering/unregistering eventfd
Date: Thu, 3 Feb 2022 15:48:35 +0000 [thread overview]
Message-ID: <f8ff62bf-4435-5da3-949a-fd337a9dfaf7@gmail.com> (raw)
In-Reply-To: <20220203151153.574032-2-usama.arif@bytedance.com>
On 2/3/22 15:11, Usama Arif wrote:
> This is done by creating a new RCU data structure (io_ev_fd) as part of
> io_ring_ctx that holds the eventfd_ctx.
>
> The function io_eventfd_signal is executed under rcu_read_lock with a
> single rcu_dereference to io_ev_fd so that if another thread unregisters
> the eventfd while io_eventfd_signal is still being executed, the
> eventfd_signal for which io_eventfd_signal was called completes
> successfully.
>
> The process of registering/unregistering eventfd is done under a lock
> so multiple threads don't enter a race condition while
> registering/unregistering eventfd.
>
> With the above approach ring quiesce can be avoided which is much more
> expensive then using RCU lock. On the system tested, io_uring_reigster with
> IORING_REGISTER_EVENTFD takes less than 1ms with RCU lock, compared to 15ms
> before with ring quiesce.
>
> Signed-off-by: Usama Arif <usama.arif@bytedance.com>
> ---
> fs/io_uring.c | 103 +++++++++++++++++++++++++++++++++++++++-----------
> 1 file changed, 80 insertions(+), 23 deletions(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 2e04f718319d..f07cfbb387a6 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -326,6 +326,12 @@ struct io_submit_state {
> struct blk_plug plug;
> };
>
> -static inline bool io_should_trigger_evfd(struct io_ring_ctx *ctx)
> +static inline bool io_should_trigger_evfd(struct io_ring_ctx *ctx, struct io_ev_fd *ev_fd)
> {
> - if (likely(!ctx->cq_ev_fd))
> + if (likely(!ev_fd))
> return false;
> if (READ_ONCE(ctx->rings->cq_flags) & IORING_CQ_EVENTFD_DISABLED)
> return false;
> return !ctx->eventfd_async || io_wq_current_is_worker();
> }
>
> +static void io_eventfd_signal(struct io_ring_ctx *ctx)
> +{
> + struct io_ev_fd *ev_fd;
> +
> + rcu_read_lock();
Please always think about the fast path, which is not set eventfd.
We don't want extra overhead here.
if (ctx->ev_fd) {
rcu_read_lock();
ev_fd = rcu_deref(...);
...
rcu_read_unlock();
}
--
Pavel Begunkov
next prev parent reply other threads:[~2022-02-03 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 15:11 [PATCH 0/2] io_uring: avoid ring quiesce in io_uring_register for eventfd opcodes Usama Arif
2022-02-03 15:11 ` [PATCH 1/2] io_uring: avoid ring quiesce while registering/unregistering eventfd Usama Arif
2022-02-03 15:48 ` Pavel Begunkov [this message]
2022-02-03 17:47 ` Usama Arif
2022-02-03 15:55 ` Jens Axboe
2022-02-03 16:49 ` Usama Arif
2022-02-03 16:58 ` Jens Axboe
2022-02-03 17:42 ` [External] " Usama Arif
2022-02-03 15:11 ` [PATCH 2/2] io_uring: avoid ring quiesce for IORING_REGISTER_EVENTFD_ASYNC Usama Arif
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=f8ff62bf-4435-5da3-949a-fd337a9dfaf7@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=fam.zheng@bytedance.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=usama.arif@bytedance.com \
/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