From: Tejun Heo <tj@kernel.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: josef@toxicpanda.com, axboe@kernel.dk, cgroups@vger.kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yukuai3@huawei.com, yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH -next 2/2] blk-throttle: fix lower control under super low iops limit
Date: Thu, 13 Jun 2024 12:32:04 -1000 [thread overview]
Message-ID: <ZmtzZKW1m6JpdfWx@slm.duckdns.org> (raw)
In-Reply-To: <20240513120848.2828797-3-yukuai1@huaweicloud.com>
Hello,
On Mon, May 13, 2024 at 08:08:48PM +0800, Yu Kuai wrote:
...
> However, if limit is quite low, the result can be 0, then
> allowed IO in the slice is 0, this will cause missing dispatch and
> control will be lower than limit.
>
> For example, set iops_limit to 5 with HD disk, and test will found that
> iops will be 3.
Hmm... can't this be solved by starting the next slice with the right
credit?
> static unsigned int tg_throtl_slice(struct throtl_grp *tg, int rw)
> {
> + if (tg->throtl_slice[rw])
> + return tg->throtl_slice[rw];
> return tg->td->throtl_slice;
Because this is a bit nasty. If we want to use difference throttling slices
for different cgroups, we might as well do it universally.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-06-13 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 12:08 [PATCH -next 0/2] " Yu Kuai
2024-05-13 12:08 ` [PATCH -next 1/2] blk-throttle: factor out a helper to get throtl_slice from tg Yu Kuai
2024-06-13 22:30 ` Tejun Heo
2024-05-13 12:08 ` [PATCH -next 2/2] blk-throttle: fix lower control under super low iops limit Yu Kuai
2024-06-13 22:32 ` Tejun Heo [this message]
2024-06-14 1:09 ` Yu Kuai
2024-06-13 2:26 ` [PATCH -next 0/2] " Yu Kuai
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=ZmtzZKW1m6JpdfWx@slm.duckdns.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.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
all inboxes | Powered by JetHome®