From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Dmitry Kadashev <dkadashev@gmail.com>,
io-uring <io-uring@vger.kernel.org>
Subject: Re: [GIT PULL] io_uring updates for 5.14-rc1
Date: Wed, 30 Jun 2021 14:21:54 -0600 [thread overview]
Message-ID: <ed4ab723-0c4d-2f44-7819-182527c98174@kernel.dk> (raw)
In-Reply-To: <CAHk-=wi9TATc=n-zrGfkEPcr7+wXx8PHe7z9-TeOmJPbisss+Q@mail.gmail.com>
On 6/30/21 2:18 PM, Linus Torvalds wrote:
> On Wed, Jun 30, 2021 at 1:14 PM Jens Axboe <axboe@kernel.dk> 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.
We certainly share that goal.
> 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.
In some ways that was almost inevitable with treading new waters, but
I'm hopeful that we're way beyond the hump on that.
I totally agree that it should not be disruptive to core code, and
I'm definitely fine rejecting those bits to avoid having that be the
case. We'll get it sorted.
--
Jens Axboe
next prev parent reply other threads:[~2021-06-30 20:22 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
2021-06-30 20:21 ` Jens Axboe [this message]
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=ed4ab723-0c4d-2f44-7819-182527c98174@kernel.dk \
--to=axboe@kernel.dk \
--cc=dkadashev@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.