From: Jens Axboe <axboe@kernel.dk>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: Ming Lei <ming.lei@redhat.com>, Mike Snitzer <snitzer@redhat.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Eric Biggers <ebiggers@google.com>,
Dmitry Monakhov <dmonakhov@openvz.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 5.20 1/4] block: add bio_rewind() API
Date: Wed, 29 Jun 2022 13:00:52 -0600 [thread overview]
Message-ID: <3e15e116-ea64-501d-1292-7b2936b19681@kernel.dk> (raw)
In-Reply-To: <20220629184001.b66bt4jnppjquzia@moria.home.lan>
On 6/29/22 12:40 PM, Kent Overstreet wrote:
> On Wed, Jun 29, 2022 at 11:16:10AM -0600, Jens Axboe wrote:
>> Not sure what Christoph change you are referring to, but all the ones
>> that I did to improve the init side were all backed by numbers I ran at
>> that time (and most/all of the commit messages will have that data). So
>> yes, it is indeed still very noticeable. Maybe not at 100K IOPS, but at
>> 10M on a core it most certainly is.
>
> I was referring to 609be1066731fea86436f5f91022f82e592ab456. You
> signed off on it, you must remember it...?
I'm sure we all remember each and every commit that gets applied,
particularly with such a precise description of the change.
>> I'm all for having solid and maintainable code, obviously, but frivolous
>> bloating of structures and more expensive setup cannot be hand waved
>> away with "it doesn't matter if we touch 3 or 6 cachelines" because we
>> obviously have a disagreement on that.
>
> I wouldn't propose inflating struct _bio_ like that. But Jens, to be
> blunt - I know we have different priorities in the way we write code.
> Your writeback throttling code was buggy for _ages_ and I had users
> hitting deadlocks there that I pinged you about, and I could not make
> heads or tails of how that code was supposed to work and not for lack
> of time spent trying!
OK Kent, you just wasted your 2nd chance here. Plonk. There are many
rebuttals that could be made here, but I won't waste my time on it, nor
would it be appropriate.
Come back when you know how to act professionally. Or don't come back
at all.
--
Jens Axboe
next prev parent reply other threads:[~2022-06-29 19:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:12 [PATCH 5.20 0/4] block/dm: add bio_rewind for improving dm requeue Ming Lei
2022-06-24 14:12 ` [PATCH 5.20 1/4] block: add bio_rewind() API Ming Lei
2022-06-26 20:14 ` Kent Overstreet
2022-06-27 7:36 ` Ming Lei
2022-06-28 4:20 ` Kent Overstreet
2022-06-28 7:42 ` Ming Lei
2022-06-28 16:16 ` Kent Overstreet
2022-06-28 18:13 ` Jens Axboe
2022-06-28 18:32 ` Kent Overstreet
2022-06-29 17:16 ` Jens Axboe
2022-06-29 18:40 ` Kent Overstreet
2022-06-29 18:51 ` Bart Van Assche
2022-06-29 19:05 ` Kent Overstreet
2022-06-29 19:37 ` Bart Van Assche
2022-06-29 19:50 ` Kent Overstreet
2022-06-29 19:59 ` Kent Overstreet
2022-06-29 19:00 ` Jens Axboe [this message]
2022-06-29 19:26 ` Kent Overstreet
2022-06-29 20:51 ` Jens Axboe
2022-06-29 0:49 ` Ming Lei
2022-06-28 4:26 ` Kent Overstreet
2022-06-28 7:49 ` Ming Lei
2022-06-28 16:36 ` Kent Overstreet
2022-06-28 17:41 ` Mike Snitzer
2022-06-28 17:52 ` Kent Overstreet
2022-06-29 6:07 ` Mike Snitzer
2022-06-29 18:11 ` Kent Overstreet
2022-06-30 0:47 ` Ming Lei
2022-06-30 0:58 ` Kent Overstreet
2022-06-30 1:14 ` Kent Overstreet
2022-07-01 3:58 ` Ming Lei
2022-07-01 21:09 ` Kent Overstreet
2022-06-29 1:02 ` Ming Lei
2022-06-26 21:37 ` [dm-devel] " Eric Biggers
2022-06-27 7:37 ` Ming Lei
2022-06-24 14:12 ` [PATCH 5.20 2/4] dm: add new helper for handling dm_io requeue Ming Lei
2022-06-24 14:12 ` [PATCH 5.20 3/4] dm: improve handling for DM_REQUEUE and AGAIN Ming Lei
2022-06-24 14:12 ` [PATCH 5.20 4/4] dm: add two stage requeue Ming Lei
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=3e15e116-ea64-501d-1292-7b2936b19681@kernel.dk \
--to=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=dmonakhov@openvz.org \
--cc=ebiggers@google.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=snitzer@redhat.com \
/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