From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, Dylan Yudaken <[email protected]>
Cc: [email protected], [email protected],
[email protected], Joel Fernandes <[email protected]>,
"Paul E . McKenney" <[email protected]>
Subject: Re: [PATCH] io_uring: use call_rcu_hurry if signaling an eventfd
Date: Thu, 15 Dec 2022 11:49:28 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 15 Dec 2022 10:41:38 -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]>
>
> [...]
Applied, thanks!
[1/1] io_uring: use call_rcu_hurry if signaling an eventfd
commit: de8f0209fe8064172a86a61537a7b21d6e5334ad
Best regards,
--
Jens Axboe
next prev parent reply other threads:[~2022-12-15 18:49 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
2022-12-15 18:49 ` Jens Axboe [this message]
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=167113016853.52282.4184815382776784529.b4-ty@kernel.dk \
[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