From: "yukuai (C)" <yukuai3@huawei.com>
To: Jan Kara <jack@suse.cz>
Cc: tj@kernel.org, axboe@kernel.dk, paolo.valente@linaro.org,
fchecconi@gmail.com, avanzini.arianna@gmail.com,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com
Subject: Re: [PATCH 2/4] block, bfq: avoid moving bfqq to it's parent bfqg
Date: Tue, 21 Dec 2021 19:08:44 +0800 [thread overview]
Message-ID: <d1c91a5f-33f3-ffad-e1ad-fb91482eb864@huawei.com> (raw)
In-Reply-To: <20211221101659.GB24748@quack2.suse.cz>
ÔÚ 2021/12/21 18:16, Jan Kara дµÀ:
> On Tue 21-12-21 11:21:33, Yu Kuai wrote:
>> Moving bfqq to it's parent bfqg is pointless.
>>
>> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
>
> Did you notice that this is happening often enough that the check is worth
> it? Where do we do this?
>
I noticed that this will happend when root group is offlined:
bfq_pd_offline
bfq_put_async_queues
__bfq_put_async_bfqq
bfq_bfqq_move
I'm not sure if there are other situations. I think bfq_bfqq_move()
is not happening often itself, thus the checking won't affect
performance.
Thanks,
Kuai
> Honza
>
>> ---
>> block/bfq-cgroup.c | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/block/bfq-cgroup.c b/block/bfq-cgroup.c
>> index 24a5c5329bcd..0f62546a72d4 100644
>> --- a/block/bfq-cgroup.c
>> +++ b/block/bfq-cgroup.c
>> @@ -645,6 +645,11 @@ void bfq_bfqq_move(struct bfq_data *bfqd, struct bfq_queue *bfqq,
>> struct bfq_group *bfqg)
>> {
>> struct bfq_entity *entity = &bfqq->entity;
>> + struct bfq_group *old_parent = bfq_group(bfqq);
>> +
>> + /* No point to move bfqq to the same group */
>> + if (old_parent == bfqg)
>> + return;
>>
>> /*
>> * Get extra reference to prevent bfqq from being freed in
>> @@ -666,7 +671,7 @@ void bfq_bfqq_move(struct bfq_data *bfqd, struct bfq_queue *bfqq,
>> bfq_deactivate_bfqq(bfqd, bfqq, false, false);
>> else if (entity->on_st_or_in_serv)
>> bfq_put_idle_entity(bfq_entity_service_tree(entity), entity);
>> - bfqg_and_blkg_put(bfqq_group(bfqq));
>> + bfqg_and_blkg_put(old_parent);
>>
>> if (entity->parent &&
>> entity->parent->last_bfqq_created == bfqq)
>> --
>> 2.31.1
>>
next prev parent reply other threads:[~2021-12-21 11:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 3:21 [PATCH 0/4] block, bfq: minor cleanup and fix Yu Kuai
[not found] ` <20211221032135.878550-1-yukuai3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-12-21 3:21 ` [PATCH 1/4] block, bfq: cleanup bfq_bfqq_to_bfqg() Yu Kuai
2021-12-21 10:15 ` Jan Kara
2021-12-21 3:21 ` [PATCH 2/4] block, bfq: avoid moving bfqq to it's parent bfqg Yu Kuai
[not found] ` <20211221032135.878550-3-yukuai3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-12-21 10:16 ` Jan Kara
2021-12-21 11:08 ` yukuai (C) [this message]
[not found] ` <d1c91a5f-33f3-ffad-e1ad-fb91482eb864-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-12-21 11:52 ` Jan Kara
2021-12-21 3:21 ` [PATCH 3/4] block, bfq: don't move oom_bfqq Yu Kuai
[not found] ` <20211221032135.878550-4-yukuai3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-12-21 10:18 ` Jan Kara
2021-12-21 3:21 ` [PATCH 4/4] block, bfq: update pos_root for idle bfq_queue in bfq_bfqq_move() Yu Kuai
[not found] ` <20211221032135.878550-5-yukuai3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-12-21 11:50 ` Jan Kara
[not found] ` <20211221115001.GD24748-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>
2021-12-22 3:12 ` yukuai (C)
[not found] ` <6ca1e924-47fa-b94e-598c-69a9549eb68e-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-12-22 14:17 ` Jan Kara
2021-12-23 1:03 ` yukuai (C)
2021-12-25 1:19 ` yukuai (C)
[not found] ` <9743fc5a-f3f0-a23a-5d21-0c04c90e90e1-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-12-25 7:44 ` yukuai (C)
2022-01-03 15:37 ` Jan Kara
2022-01-07 1:04 ` yukuai (C)
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=d1c91a5f-33f3-ffad-e1ad-fb91482eb864@huawei.com \
--to=yukuai3@huawei.com \
--cc=avanzini.arianna@gmail.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=fchecconi@gmail.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=tj@kernel.org \
--cc=yi.zhang@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