From: Kemeng Shi <shikemeng@huawei.com>
To: <tj@kernel.org>, <josef@toxicpanda.com>, <axboe@kernel.dk>
Cc: <cgroups@vger.kernel.org>, <linux-block@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <shikemeng@huawei.com>
Subject: [PATCH v2 00/10] A few bugfix and cleanup patches for blk-throttle
Date: Tue, 29 Nov 2022 11:01:37 +0800 [thread overview]
Message-ID: <20221129030147.27400-1-shikemeng@huawei.com> (raw)
Hi, this series contain a few patches to fix problem when on the default
hierarchy, corrent comment and so on. More detail can be found in
respective changelogs. Thanks.
---
V1->V2:
-Thanks for the review and advice from Tejun. The corrected comment of
"blk-throttle: correct stale comment in throtl_pd_init" and the
solution of "blk-throttle: Fix that bps of child could exceed bps
limited in parent" are from reply of Tejun.
-Collect Ack from Tejun.
-Fix the compile problem when CONFIG_BLK_DEV_THROTTLING_LOW is set.
-Drop "blk-throttle: Limit whole system if root group is configured
when on the default hierarchy", "blk-throttle: remove unnecessary check
for validation of limit index" and "blk-throttle: remove unused variable
td in tg_update_has_rules"
-Add "blk-throttle: correct stale comment in throtl_pd_init" and
"blk-throttle: avoid dead code in throtl_hierarchy_can_upgrade"
-Use solution that set the BIO_BPS_THROTTLED flag only when the bio
traversed the entire tree to fix that bps of child could exceed bps
limited in parent in patch 2/10.
-Improve the description and comment of most commits.
---
Kemeng Shi (10):
blk-throttle: correct stale comment in throtl_pd_init
blk-throttle: Fix that bps of child could exceed bps limited in parent
blk-throttle: ignore cgroup without io queued in
blk_throtl_cancel_bios
blk-throttle: correct calculation of wait time in tg_may_dispatch
blk-throttle: simpfy low limit reached check in throtl_tg_can_upgrade
blk-throttle: fix typo in comment of throtl_adjusted_limit
blk-throttle: remove incorrect comment for tg_last_low_overflow_time
blk-throttle: remove repeat check of elapsed time from last upgrade in
throtl_hierarchy_can_downgrade
blk-throttle: Use more siutable time_after check for update of
slice_start
blk-throttle: avoid dead code in throtl_hierarchy_can_upgrade
block/blk-throttle.c | 104 +++++++++++++++++++++++--------------------
1 file changed, 56 insertions(+), 48 deletions(-)
--
2.30.0
next reply other threads:[~2022-11-29 3:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 3:01 Kemeng Shi [this message]
2022-11-29 3:01 ` [PATCH v2 01/10] blk-throttle: correct stale comment in throtl_pd_init Kemeng Shi
2022-11-30 21:08 ` Tejun Heo
2022-11-29 3:01 ` [PATCH v2 02/10] blk-throttle: Fix that bps of child could exceed bps limited in parent Kemeng Shi
2022-11-30 21:09 ` Tejun Heo
2022-11-29 3:01 ` [PATCH v2 03/10] blk-throttle: ignore cgroup without io queued in blk_throtl_cancel_bios Kemeng Shi
2022-11-29 3:01 ` [PATCH v2 04/10] blk-throttle: correct calculation of wait time in tg_may_dispatch Kemeng Shi
2022-11-30 21:27 ` Tejun Heo
2022-11-29 3:01 ` [PATCH v2 05/10] blk-throttle: simpfy low limit reached check in throtl_tg_can_upgrade Kemeng Shi
2022-11-30 22:09 ` Tejun Heo
2022-11-29 3:01 ` [PATCH v2 06/10] blk-throttle: fix typo in comment of throtl_adjusted_limit Kemeng Shi
2022-11-29 3:01 ` [PATCH v2 07/10] blk-throttle: remove incorrect comment for tg_last_low_overflow_time Kemeng Shi
2022-11-29 3:01 ` [PATCH v2 08/10] blk-throttle: remove repeat check of elapsed time from last upgrade in throtl_hierarchy_can_downgrade Kemeng Shi
2022-11-30 21:34 ` Tejun Heo
2022-11-29 3:01 ` [PATCH v2 09/10] blk-throttle: Use more siutable time_after check for update of slice_start Kemeng Shi
2022-11-30 21:34 ` Tejun Heo
2022-11-29 3:01 ` [PATCH v2 10/10] blk-throttle: avoid dead code in throtl_hierarchy_can_upgrade Kemeng Shi
2022-11-30 21:36 ` Tejun Heo
2022-12-01 1:36 ` Kemeng Shi
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=20221129030147.27400-1-shikemeng@huawei.com \
--to=shikemeng@huawei.com \
--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=tj@kernel.org \
/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