From: Linus Torvalds <[email protected]>
To: Jens Axboe <[email protected]>,
"Paul E. McKenney" <[email protected]>,
Tejun Heo <[email protected]>
Cc: io-uring <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [GIT PULL] io_uring fixes for 5.6-rc
Date: Fri, 13 Mar 2020 13:18:30 -0700 [thread overview]
Message-ID: <CAHk-=wgGN-9dmso4L+6RWdouEg4zQfd74m23K6c9E_=Qua+H1Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Fri, Mar 13, 2020 at 10:50 AM Jens Axboe <[email protected]> wrote:
>
> Just a single fix here, improving the RCU callback ordering from last
> week. After a bit more perusing by Paul, he poked a hole in the
> original.
Ouch.
If I read this patch correctly, you're now adding a rcu_barrier() onto
the system workqueue for each io_uring context freeing op.
This makes me worry:
- I think system_wq is unordered, so does it even guarantee that the
rcu_barrier happens after whatever work you're expecting it to be
after?
Or is it using a workqueue not because it wants to serialize with any
other work, but because it needs to use rcu_barrier in a context where
it can't sleep?
But the commit message does seem to imply that ordering is important..
- doesn't this have the potential to flood the system_wq be full of
flushing things that all could take a while..
I've pulled it, and it may all be correct, just chalk this message up
to "Linus got nervous looking at it".
Added Paul and Tejun to the participants explicitly.
Linus
next prev parent reply other threads:[~2020-03-13 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 17:50 [GIT PULL] io_uring fixes for 5.6-rc Jens Axboe
2020-03-13 20:18 ` Linus Torvalds [this message]
2020-03-13 20:33 ` Paul E. McKenney
2020-03-13 21:33 ` Jens Axboe
2020-03-13 20:25 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-03-21 18:38 Jens Axboe
2020-03-21 19:15 ` pr-tracker-bot
2020-03-07 19:16 Jens Axboe
2020-03-07 20:25 ` pr-tracker-bot
2020-02-28 18:42 Jens Axboe
2020-02-28 19:55 ` pr-tracker-bot
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='CAHk-=wgGN-9dmso4L+6RWdouEg4zQfd74m23K6c9E_=Qua+H1Q@mail.gmail.com' \
[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