public inbox for [email protected]
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <[email protected]>
To: Dylan Yudaken <[email protected]>
Cc: Jens Axboe <[email protected]>,
	Pavel Begunkov <[email protected]>,
	[email protected], [email protected],
	[email protected], Joel Fernandes <[email protected]>
Subject: Re: [PATCH] io_uring: use call_rcu_hurry if signaling an eventfd
Date: Thu, 15 Dec 2022 10:44:27 -0800	[thread overview]
Message-ID: <20221215184427.GI4001@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <[email protected]>

On Thu, Dec 15, 2022 at 10:41:38AM -0800, Dylan Yudaken wrote:
> io_uring uses call_rcu in the case it needs to signal an eventfd as a
> result of an eventfd signal, since recursing eventfd signals are not
> allowed. This should be calling the new call_rcu_hurry API to not delay
> the signal.
> 
> Signed-off-by: Dylan Yudaken <[email protected]>
> 
> Cc: Joel Fernandes (Google) <[email protected]>
> Cc: Paul E. McKenney <[email protected]>

Looks good!

Acked-by: Paul E. McKenney <[email protected]>

> ---
>  io_uring/io_uring.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
> index b521186efa5c..2cb8c665bab1 100644
> --- a/io_uring/io_uring.c
> +++ b/io_uring/io_uring.c
> @@ -538,7 +538,7 @@ static void io_eventfd_signal(struct io_ring_ctx *ctx)
>  	} else {
>  		atomic_inc(&ev_fd->refs);
>  		if (!atomic_fetch_or(BIT(IO_EVENTFD_OP_SIGNAL_BIT), &ev_fd->ops))
> -			call_rcu(&ev_fd->rcu, io_eventfd_ops);
> +			call_rcu_hurry(&ev_fd->rcu, io_eventfd_ops);
>  		else
>  			atomic_dec(&ev_fd->refs);
>  	}
> 
> base-commit: 041fae9c105ae342a4245cf1e0dc56a23fbb9d3c
> -- 
> 2.30.2
> 

  reply	other threads:[~2022-12-15 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 18:41 [PATCH] io_uring: use call_rcu_hurry if signaling an eventfd Dylan Yudaken
2022-12-15 18:44 ` Paul E. McKenney [this message]
2022-12-15 18:49 ` Jens Axboe
2022-12-15 18:51   ` Joel Fernandes

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=20221215184427.GI4001@paulmck-ThinkPad-P17-Gen-1 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [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