From: Linus Torvalds <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Al Viro <[email protected]>,
Dmitry Kadashev <[email protected]>,
io-uring <[email protected]>
Subject: Re: [GIT PULL] io_uring updates for 5.14-rc1
Date: Wed, 30 Jun 2021 13:18:41 -0700 [thread overview]
Message-ID: <CAHk-=wi9TATc=n-zrGfkEPcr7+wXx8PHe7z9-TeOmJPbisss+Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Wed, Jun 30, 2021 at 1:14 PM Jens Axboe <[email protected]> wrote:
>
> I think you're being very unfair here, last release was pretty
> uneventful, and of course 5.12 was a bit too exciting with the
> thread changes, but that was both expected and a necessary evil.
The last one may have been uneventful, but I really want to keep it that way.
And the threading changes were an improvement overall, but they were
by no means the first time io_uring was flaky and had issues. It has
caused a _lot_ of churn over the years.
And I refuse to have that churn now affect fs/namei.c
This had better be done right, or not at all.
Linus
next prev parent reply other threads:[~2021-06-30 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 20:43 [GIT PULL] io_uring updates for 5.14-rc1 Jens Axboe
2021-06-30 20:05 ` Linus Torvalds
2021-06-30 20:14 ` Jens Axboe
2021-06-30 20:18 ` Linus Torvalds [this message]
2021-06-30 20:21 ` Jens Axboe
2021-07-02 11:32 ` Dmitry Kadashev
2021-07-02 18:33 ` Linus Torvalds
2021-07-03 15:26 ` Dmitry Kadashev
2021-07-05 21:40 ` Linus Torvalds
2021-07-06 12:06 ` Dmitry Kadashev
-- strict thread matches above, loose matches on Subject: below --
2021-07-01 15:24 Jens Axboe
2021-07-01 19:20 ` 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-=wi9TATc=n-zrGfkEPcr7+wXx8PHe7z9-TeOmJPbisss+Q@mail.gmail.com' \
[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