From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: abuehaze@amazon.com, linux-block@vger.kernel.org, ming.lei@redhat.com
Subject: Re: [PATCH, RFC] block: always use a list_head for requests
Date: Thu, 12 Jun 2025 05:53:06 -0600 [thread overview]
Message-ID: <ab5bd614-a873-4228-968f-e9086ad1ba38@kernel.dk> (raw)
In-Reply-To: <20250612074245.2718371-1-hch@lst.de>
On 6/12/25 1:42 AM, Christoph Hellwig wrote:
> Turn the remaining lists of requests into the standard doubly linked
> list. This removes a lot of hairy list manipulation code and allows
> east reverse walking of the lists, which will be needed to improve
> merging.
>
> XXX: the ublk queue_rqs code is pretty much broken here, because
> it's so different from the other drivers and I don't understand it.
First of all, we're definitely not doing this for 6.16-rc, and secondly
it'd need to be properly tested in terms of performance implications as
well.
I'm somewhat annoyed that ordered plug lists turned into this, which I
already strongly suspected would be the case back then. And doubly so
that a really basic performance regression was also caused by that, and
then the proposed "fix" is to go further into the "let's slow down the
fast path" of code. Yes deleting some code is nice, but let's not
pretend that it's free.
--
Jens Axboe
next prev parent reply other threads:[~2025-06-12 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 7:42 [PATCH, RFC] block: always use a list_head for requests Christoph Hellwig
2025-06-12 11:53 ` Jens Axboe [this message]
2025-06-12 12:10 ` Mohamed Abuelfotoh, Hazem
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=ab5bd614-a873-4228-968f-e9086ad1ba38@kernel.dk \
--to=axboe@kernel.dk \
--cc=abuehaze@amazon.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@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