[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6ab1172f-2c9a-ede3-8020-13c73b91db84@huaweicloud.com>
Date: Mon, 22 Apr 2024 17:42:18 +0800
From: Yu Kuai <yukuai1@...weicloud.com>
To: 周泰宇 <zhoutaiyu@...ishou.com>,
Yu Kuai <yukuai1@...weicloud.com>, "tj@...nel.org" <tj@...nel.org>
Cc: "josef@...icpanda.com" <josef@...icpanda.com>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"cgroups@...r.kernel.org" <cgroups@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: [PATCH] blk-throttle: fix repeat limit on bio with
BIO_BPS_THROTTLED
Hi,
在 2024/04/22 11:33, 周泰宇 写道:
>>> /* throtl is FIFO - if bios are already queued, should queue */
>>> - if (sq->nr_queued[rw])
>>> + if (sq->nr_queued[rw] && !bio_flagged(bio, BIO_BPS_THROTTLED))
>> No, this change is wrong. Split IO will not be throttled by iops limit
> anymore.
>
> After this change, the split IO will be throttled by iops limit again if it reaches a tg's iops limit and will not be throttled in any cases if the sq->queue is not empty.
Forgot to reply here,
The ponit here is that you break the rules about FIFO, blk-throttle
only judge the bio from head if it's within limit. Current code to judge
if tg iops reaches limit on the condition that no bio is throttled. And
throtl time is always caculated by first throttled bio. But this patch
will ignore throttled bio case, and that's why I said IO will not be
throttled by iops limist anymore. You can test this with bps limit
disabled.
Thanks,
Kuai
Powered by blists - more mailing lists