From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bvanassche@acm.org>,
Zhen Lei <thunder.leizhen@huawei.com>,
linux-block <linux-block@vger.kernel.org>
Cc: Damien Le Moal <damien.lemoal@wdc.com>
Subject: Re: [PATCH] block/mq-deadline: Speed up the dispatch of low-priority requests
Date: Thu, 26 Aug 2021 17:51:10 -0600 [thread overview]
Message-ID: <0ef7865d-a9ce-c5d9-ff7f-c0ef58de3d21@kernel.dk> (raw)
In-Reply-To: <59c19a63-f321-94e8-cb31-87e88bd4e3d5@acm.org>
On 8/26/21 5:49 PM, Bart Van Assche wrote:
> On 8/26/21 11:45 AM, Jens Axboe wrote:
>> Just ran a quick test here, and I go from 3.55M IOPS to 1.23M switching
>> to deadline, of which 37% of the overhead is from dd_dispatch().
>>
>> With the posted patch applied, it runs at 2.3M IOPS with mq-deadline,
>> which is a lot better. This is on my 3970X test box, so 32 cores, 64
>> threads.
>
> Hi Jens,
>
> With the script below, queue depth >= 2 and an improved version of
> Zhen's patch I see 970 K IOPS with the mq-deadline scheduler in an
> 8 core VM (i7-4790 CPU). In other words, more IOPS than what Zhen
> reported with fewer CPU cores. Is that good enough?
That depends, what kind of IOPS are you getting if you revert the
original change?
--
Jens Axboe
next prev parent reply other threads:[~2021-08-26 23:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 14:40 [PATCH] block/mq-deadline: Speed up the dispatch of low-priority requests Zhen Lei
2021-08-26 18:09 ` Bart Van Assche
2021-08-26 18:13 ` Jens Axboe
2021-08-26 18:45 ` Jens Axboe
2021-08-26 19:17 ` Bart Van Assche
2021-08-26 19:32 ` Jens Axboe
2021-08-26 23:49 ` Bart Van Assche
2021-08-26 23:51 ` Jens Axboe [this message]
2021-08-27 0:03 ` Bart Van Assche
2021-08-27 0:05 ` Jens Axboe
2021-08-27 0:58 ` Bart Van Assche
2021-08-27 2:48 ` Bart Van Assche
2021-08-27 3:13 ` Jens Axboe
2021-08-27 4:49 ` Damien Le Moal
2021-08-27 14:34 ` Bart Van Assche
2021-08-29 23:02 ` Damien Le Moal
2021-08-30 2:31 ` Keith Busch
2021-08-30 3:03 ` Damien Le Moal
2021-08-30 2:40 ` Bart Van Assche
2021-08-30 3:07 ` Damien Le Moal
2021-08-30 17:14 ` Bart Van Assche
2021-08-30 21:42 ` Damien Le Moal
2021-08-28 1:45 ` Leizhen (ThunderTown)
2021-08-28 2:19 ` Bart Van Assche
2021-08-28 2:42 ` Leizhen (ThunderTown)
2021-08-28 13:14 ` Leizhen (ThunderTown)
2021-08-28 1:59 ` Leizhen (ThunderTown)
2021-08-28 2:41 ` Bart Van Assche
2021-08-27 2:30 ` Damien Le Moal
2021-08-28 2:14 ` Leizhen (ThunderTown)
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=0ef7865d-a9ce-c5d9-ff7f-c0ef58de3d21@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=thunder.leizhen@huawei.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 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.