From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Bart Van Assche <bvanassche@acm.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
<linux-kernel@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: Sat, 28 Aug 2021 09:59:53 +0800 [thread overview]
Message-ID: <b653a431-997b-0d94-2823-779f877c314f@huawei.com> (raw)
In-Reply-To: <fc1f2664-fc4f-7b3e-5542-d9e4800a5bde@acm.org>
On 2021/8/27 2:09, Bart Van Assche wrote:
> On 8/26/21 7:40 AM, Zhen Lei wrote:
>> lock protection needs to be added only in
>> dd_finish_request(), which is unlikely to cause significant performance
>> side effects.
>
> Not sure the above is correct. Every new atomic instruction has a measurable
> performance overhead. But I guess in this case that overhead is smaller than
> the time needed to sum 128 per-CPU variables.
>
>> Tested on my 128-core board with two ssd disks.
>> fio bs=4k rw=read iodepth=128 cpus_allowed=0-95 <others>
>> Before:
>> [183K/0/0 iops]
>> [172K/0/0 iops]
>>
>> After:
>> [258K/0/0 iops]
>> [258K/0/0 iops]
>
> Nice work!
>
>> Fixes: fb926032b320 ("block/mq-deadline: Prioritize high-priority requests")
>
> Shouldn't the Fixes: tag be used only for patches that modify functionality?
> I'm not sure it is appropriate to use this tag for performance improvements.
>
>> struct deadline_data {
>> @@ -277,9 +278,9 @@ deadline_move_request(struct deadline_data *dd, struct dd_per_prio *per_prio,
>> }
>>
>> /* Number of requests queued for a given priority level. */
>> -static u32 dd_queued(struct deadline_data *dd, enum dd_prio prio)
>> +static __always_inline u32 dd_queued(struct deadline_data *dd, enum dd_prio prio)
>> {
>> - return dd_sum(dd, inserted, prio) - dd_sum(dd, completed, prio);
>> + return dd->per_prio[prio].nr_queued;
>> }
>
> Please leave out "__always_inline". Modern compilers are smart enough to
> inline this function without using the "inline" keyword.
Yes.
>
>> @@ -711,6 +712,8 @@ static void dd_insert_request(struct blk_mq_hw_ctx *hctx, struct request *rq,
>>
>> prio = ioprio_class_to_prio[ioprio_class];
>> dd_count(dd, inserted, prio);
>> + per_prio = &dd->per_prio[prio];
>> + per_prio->nr_queued++;
>>
>> if (blk_mq_sched_try_insert_merge(q, rq, &free)) {
>> blk_mq_free_requests(&free);
>
> I think the above is wrong - nr_queued should not be incremented if the
> request is merged into another request. Please move the code that increments
> nr_queued past the above if-statement.
So dd_count(dd, inserted, prio) needs to be moved behind "if-statement" as well?
>
> Thanks,
>
> Bart.
> .
>
next prev parent reply other threads:[~2021-08-28 2:00 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
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) [this message]
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=b653a431-997b-0d94-2823-779f877c314f@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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