From: Tejun Heo <tj@kernel.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: mkoutny@suse.com, axboe@kernel.dk, ming.lei@redhat.com,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH RESEND v6 1/8] blk-throttle: fix that io throttle can only work for single bio
Date: Fri, 29 Jul 2022 08:04:42 -1000 [thread overview]
Message-ID: <YuQhOjo02RX7uZ0K@slm.duckdns.org> (raw)
In-Reply-To: <7f01aba1-43ab-38ab-5755-7ac22d0a78d5@huaweicloud.com>
Hello,
On Fri, Jul 29, 2022 at 02:32:36PM +0800, Yu Kuai wrote:
> We need to make sure following conditions is always hold:
>
> 1) If a bio is splited, iops limits should count multiple times, while
> bps limits should only count once.
> 2) If a bio is issued while some bios are already throttled, bps limits
> should not be ignored.
>
> commit 9f5ede3c01f9 ("block: throttle split bio in case of iops limit")
> fixes that 1) is not hold, while it breaks 2). Root cause is that such
> bio will be flaged in __blk_throtl_bio(), and later
> tg_with_in_bps_limit() will skip flaged bio.
>
> In order to fix this problem, at first, I change that flaged bio won't
> be skipped in tg_with_in_bps_limit():
>
> - if (!bio_flagged(bio, BIO_THROTTLED)) {
> - tg->bytes_disp[rw] += bio_size;
> - tg->last_bytes_disp[rw] += bio_size;
> - }
> -
> + tg->bytes_disp[rw] += bio_size;
> + tg->last_bytes_disp[rw] += bio_size;
>
> However, this will break that bps limits should only count once. Thus I
> try to restore the overaccounting in __blk_throtl_bio() in such case:
>
> + if (bio_flagged(bio, BIO_THROTTLED)) {
> + unsigned int bio_size = throtl_bio_data_size(bio);
> +
> + if (tg->bytes_disp[rw] >= bio_size)
> + tg->bytes_disp[rw] -= bio_size;
> + if (tg->last_bytes_disp[rw] >= bio_size)
> + tg->last_bytes_disp[rw] -= bio_size;
> + }
>
> If new slice is not started, then the decrement should make sure this
> bio won't be counted again. However, if new slice is started and the
> condition 'bytes_disp >= bio_size' doesn't hold, this bio will end up
> accounting twice.
>
> Pleas let me know if you think this suituation is problematic, I'll try
> to figure out a new way...
While a bit tricky, I think it's fine but please add comments in the code
explaining what's going on and why. Also, can you please explain why
__blk_throtl_bio() being skipped when iops limit is not set doesn't skew the
result?
Thanks.
--
tejun
next prev parent reply other threads:[~2022-07-29 18:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 9:34 [PATCH RESEND v6 0/8] bugfix and cleanup for blk-throttle Yu Kuai
2022-07-01 9:34 ` [PATCH RESEND v6 1/8] blk-throttle: fix that io throttle can only work for single bio Yu Kuai
2022-07-27 18:27 ` Tejun Heo
2022-07-29 6:32 ` Yu Kuai
2022-07-29 18:04 ` Tejun Heo [this message]
2022-07-30 1:06 ` Yu Kuai
2022-07-01 9:34 ` [PATCH RESEND v6 2/8] blk-throttle: prevent overflow while calculating wait time Yu Kuai
2022-07-27 18:28 ` Tejun Heo
2022-07-28 10:23 ` Yu Kuai
2022-07-01 9:34 ` [PATCH RESEND v6 3/8] blk-throttle: factor out code to calculate ios/bytes_allowed Yu Kuai
2022-07-01 9:34 ` [PATCH RESEND v6 4/8] blk-throttle: fix io hung due to config updates Yu Kuai
2022-07-27 18:39 ` Tejun Heo
2022-07-28 9:33 ` Michal Koutný
2022-07-28 10:34 ` Yu Kuai
2022-07-28 16:55 ` Tejun Heo
2022-07-01 9:34 ` [PATCH RESEND v6 5/8] blk-throttle: use 'READ/WRITE' instead of '0/1' Yu Kuai
2022-07-27 18:39 ` Tejun Heo
2022-07-01 9:34 ` [PATCH RESEND v6 6/8] blk-throttle: calling throtl_dequeue/enqueue_tg in pairs Yu Kuai
2022-07-27 18:40 ` Tejun Heo
2022-07-01 9:34 ` [PATCH RESEND v6 7/8] blk-throttle: cleanup tg_update_disptime() Yu Kuai
2022-07-27 18:42 ` Tejun Heo
2022-07-01 9:34 ` [PATCH RESEND v6 8/8] blk-throttle: clean up flag 'THROTL_TG_PENDING' Yu Kuai
2022-07-27 18:44 ` Tejun Heo
2022-07-28 11:03 ` Yu Kuai
2022-07-10 2:39 ` [PATCH RESEND v6 0/8] bugfix and cleanup for blk-throttle Yu Kuai
2022-07-10 2:40 ` Yu Kuai
2022-07-20 11:45 ` Yu Kuai
2022-07-27 12:12 ` 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=YuQhOjo02RX7uZ0K@slm.duckdns.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mkoutny@suse.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;
as well as URLs for NNTP newsgroup(s).