From: Yu Kuai <yukuai1@huaweicloud.com>
To: Nilay Shroff <nilay@linux.ibm.com>,
Yu Kuai <hailan@yukuai.org.cn>, Yu Kuai <yukuai1@huaweicloud.com>,
ming.lei@redhat.com, axboe@kernel.dk
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, yangerkun@huawei.com,
johnny.chenyi@huawei.com, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH for-6.18/block 06/10] blk-mq: split bitmap grow and resize case in blk_mq_update_nr_requests()
Date: Wed, 10 Sep 2025 14:42:18 +0800 [thread overview]
Message-ID: <bd4e6dfb-fa9c-d36a-5ed5-4cf6411f00a6@huaweicloud.com> (raw)
In-Reply-To: <a4fd99c3-faa6-4c6d-b7a5-4f32d3eed40b@linux.ibm.com>
Hi,
在 2025/09/10 14:30, Nilay Shroff 写道:
>
>
> On 9/9/25 10:09 PM, Yu Kuai wrote:
>> Hi,
>>
>> 在 2025/9/9 20:18, Nilay Shroff 写道:
>>>
>>> On 9/8/25 11:45 AM, Yu Kuai wrote:
>>>> From: Yu Kuai <yukuai3@huawei.com>
>>>>
>>>> No functional changes are intended, make code cleaner and prepare to fix
>>>> the grow case in following patches.
>>>>
>>>> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
>>>> ---
>>>> block/blk-mq.c | 28 ++++++++++++++++------------
>>>> 1 file changed, 16 insertions(+), 12 deletions(-)
>>>>
>>>> diff --git a/block/blk-mq.c b/block/blk-mq.c
>>>> index 1ff6370f7314..82fa81036115 100644
>>>> --- a/block/blk-mq.c
>>>> +++ b/block/blk-mq.c
>>>> @@ -4931,21 +4931,25 @@ int blk_mq_update_nr_requests(struct request_queue *q, unsigned int nr)
>>>> blk_mq_tag_update_sched_shared_tags(q);
>>>> else
>>>> blk_mq_tag_resize_shared_tags(set, nr);
>>>> - } else {
>>>> + } else if (!q->elevator) {
>>>> queue_for_each_hw_ctx(q, hctx, i) {
>>>> if (!hctx->tags)
>>>> continue;
>>>> - /*
>>>> - * If we're using an MQ scheduler, just update the
>>>> - * scheduler queue depth. This is similar to what the
>>>> - * old code would do.
>>>> - */
>>>> - if (hctx->sched_tags)
>>>> - ret = blk_mq_tag_update_depth(hctx,
>>>> - &hctx->sched_tags, nr);
>>>> - else
>>>> - ret = blk_mq_tag_update_depth(hctx,
>>>> - &hctx->tags, nr);
>>>> + sbitmap_queue_resize(&hctx->tags->bitmap_tags,
>>>> + nr - hctx->tags->nr_reserved_tags);
>>>> + }
>>>> + } else if (nr <= q->elevator->et->nr_requests) {
>>>> + queue_for_each_hw_ctx(q, hctx, i) {
>>>> + if (!hctx->sched_tags)
>>>> + continue;
>>>> + sbitmap_queue_resize(&hctx->sched_tags->bitmap_tags,
>>>> + nr - hctx->sched_tags->nr_reserved_tags);
>>>> + }
>>>> + } else {
>>>> + queue_for_each_hw_ctx(q, hctx, i) {
>>>> + if (!hctx->sched_tags)
>>>> + continue;
>>>> + blk_mq_tag_update_depth(hctx, &hctx->sched_tags, nr);
>>>> if (ret)
>>>> goto out;
>>>> }
>>> The above code is good however can this be bit simplified?
>>> It's a bit difficult to follow through all nesting and so
>>> could it be simplified as below:
>>>
>>> if (shared-tags) {
>>> if (elevator)
>>> // resize sched-shared-tags bitmap
>>> else
>>> // resize shared-tags bitmap
>>> } else {
>>> // non-shared tags
>>> if (elevator) {
>>> if (new-depth-is-less-than-the-current-depth)
>>> // resize sched-tags bitmap
>>> else
>>> // handle sched tags grow
>>> } else
>>> // resize tags bitmap
>>> }
>>
>> AFAIK, if - else if chain should be better than nested if - else, right?
>>
>> If you don't mind, I can add comments to each else if chain to make code cleaner:
>>
>> if () {
>> /* shared tags */
>> ...
>> } else if () {
>> /* non-shared tags and elevator is none */
>> ...
>> } else if () {
>> /* non-shared tags and elevator is not none, nr_requests doesn't grow */
>> ...
>> } else () {
>> /* non-shared tags and elevator is not none, nr_requests grow */
>> ...
>> }
>>
> Yeah, I am good with the proper comments as well so that it'd be easy
> for anyone reviewing the code later to understand what those all nested
> if-else conditions meant.
>
Ok, I'll do that in the next version.
Thanks for the review!
Kuai
> Thanks,
> --Nilay
>
> .
>
next prev parent reply other threads:[~2025-09-10 6:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 6:15 [PATCH for-6.18/block 00/10] cleanup and fixes for updating nr_requests Yu Kuai
2025-09-08 6:15 ` [PATCH for-6.18/block 01/10] blk-mq: remove useless checking in queue_requests_store() Yu Kuai
2025-09-09 11:34 ` Nilay Shroff
2025-09-08 6:15 ` [PATCH for-6.18/block 02/10] blk-mq: remove useless checkings in blk_mq_update_nr_requests() Yu Kuai
2025-09-09 11:35 ` Nilay Shroff
2025-09-08 6:15 ` [PATCH for-6.18/block 03/10] blk-mq: check invalid nr_requests in queue_requests_store() Yu Kuai
2025-09-09 11:36 ` Nilay Shroff
2025-09-08 6:15 ` [PATCH for-6.18/block 04/10] blk-mq: convert to serialize updating nr_requests with update_nr_hwq_lock Yu Kuai
2025-09-09 6:29 ` Nilay Shroff
2025-09-09 6:38 ` Yu Kuai
2025-09-09 6:52 ` Nilay Shroff
2025-09-09 7:16 ` Yu Kuai
2025-09-09 9:26 ` Nilay Shroff
2025-09-09 9:36 ` Yu Kuai
2025-09-09 10:11 ` Nilay Shroff
2025-09-09 10:42 ` Yu Kuai
2025-09-09 11:32 ` Nilay Shroff
2025-09-09 11:40 ` Nilay Shroff
2025-09-08 6:15 ` [PATCH for-6.18/block 05/10] blk-mq: cleanup shared tags case in blk_mq_update_nr_requests() Yu Kuai
2025-09-09 11:58 ` Nilay Shroff
2025-09-08 6:15 ` [PATCH for-6.18/block 06/10] blk-mq: split bitmap grow and resize " Yu Kuai
2025-09-09 12:18 ` Nilay Shroff
2025-09-09 16:39 ` Yu Kuai
2025-09-10 6:30 ` Nilay Shroff
2025-09-10 6:42 ` Yu Kuai [this message]
2025-09-08 6:15 ` [PATCH for-6.18/block 07/10] blk-mq-sched: add new parameter nr_requests in blk_mq_alloc_sched_tags() Yu Kuai
2025-09-09 12:19 ` Nilay Shroff
2025-09-08 6:15 ` [PATCH for-6.18/block 08/10] blk-mq: fix potential deadlock while nr_requests grown Yu Kuai
2025-09-09 6:39 ` Nilay Shroff
2025-09-09 7:37 ` Yu Kuai
2025-09-09 9:36 ` Nilay Shroff
2025-09-09 12:21 ` Nilay Shroff
2025-09-10 7:46 ` Yu Kuai
2025-09-08 6:15 ` [PATCH for-6.18/block 09/10] blk-mq: remove blk_mq_tag_update_depth() Yu Kuai
2025-09-09 12:35 ` Nilay Shroff
2025-09-08 6:15 ` [PATCH for-6.18/block 10/10] blk-mq: fix stale nr_requests documentation Yu Kuai
2025-09-09 12:35 ` Nilay Shroff
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=bd4e6dfb-fa9c-d36a-5ed5-4cf6411f00a6@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=axboe@kernel.dk \
--cc=hailan@yukuai.org.cn \
--cc=johnny.chenyi@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=nilay@linux.ibm.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox