From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Song Liu <song@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-raid@vger.kernel.org,
stable@vger.kernel.org, Larkin Lowrey <llowrey@nuclearwinter.com>,
Wilson Jonathan <i400sjon@gmail.com>,
Roger Heflin <rogerheflin@gmail.com>
Subject: Re: [PATCH] block: check more requests for multiple_queues in blk_attempt_plug_merge
Date: Fri, 11 Mar 2022 22:41:56 +0100 [thread overview]
Message-ID: <11a4c611-ed0c-789f-b5d0-8a127539daf1@molgen.mpg.de> (raw)
In-Reply-To: <CAPhsuW492+zrVCyckgct_ju+5V_2grn4-s--TU2QVA7pkYtyzA@mail.gmail.com>
Dear Song,
Am 11.03.22 um 17:59 schrieb Song Liu:
> On Fri, Mar 11, 2022 at 6:16 AM Jens Axboe <axboe@kernel.dk> wrote:
>>
>> On 3/10/22 5:07 PM, Jens Axboe wrote:
>>> In any case, just doing larger reads would likely help quite a bit, but
>>> would still be nice to get to the bottom of why we're not seeing the
>>> level of merging we expect.
>>
>> Song, can you try this one? It'll do the dispatch in a somewhat saner
>> fashion, bundling identical queues. And we'll keep iterating the plug
>> list for a merge if we have multiple disks, until we've seen a queue
>> match and checked.
>
> This one works great! We are seeing 99% read request merge and
> 500kB+ average read size. The original patch in this thread only got
> 88% and 34kB for these two metrics.
Nice. I am curious, how these metrics can be obtained?
[…]
Kind regards,
Paul
next prev parent reply other threads:[~2022-03-11 22:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 6:42 [PATCH] block: check more requests for multiple_queues in blk_attempt_plug_merge Song Liu
2022-03-10 6:48 ` Christoph Hellwig
2022-03-10 7:23 ` Song Liu
2022-03-10 22:10 ` Song Liu
2022-03-10 22:12 ` Song Liu
2022-03-10 22:15 ` Jens Axboe
2022-03-10 22:37 ` Song Liu
2022-03-10 23:02 ` Jens Axboe
2022-03-10 23:33 ` Song Liu
2022-03-11 0:07 ` Jens Axboe
2022-03-11 0:31 ` Song Liu
2022-03-11 0:36 ` Jens Axboe
2022-03-11 0:38 ` Jens Axboe
2022-03-11 1:14 ` Ming Lei
2022-03-11 1:21 ` Jens Axboe
2022-03-11 1:32 ` Ming Lei
2022-03-11 1:35 ` Jens Axboe
2022-03-11 8:09 ` Wols Lists
2022-03-11 14:16 ` Jens Axboe
2022-03-11 16:59 ` Song Liu
2022-03-11 21:41 ` Paul Menzel [this message]
2022-03-11 22:40 ` Song Liu
2022-03-11 11:30 ` Wilson Jonathan
2022-03-11 15:58 ` Wols Lists
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=11a4c611-ed0c-789f-b5d0-8a127539daf1@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=axboe@kernel.dk \
--cc=i400sjon@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=llowrey@nuclearwinter.com \
--cc=rogerheflin@gmail.com \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).