From: Tang Yizhou <tangyeechou@gmail.com>
To: Tao Cui <cui.tao@linux.dev>,
axboe@kernel.dk, linux-block@vger.kernel.org
Cc: tj@kernel.org, josef@toxicpanda.com, yukuai3@huawei.com,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Tao Cui <cuitao@kylinos.cn>
Subject: Re: [PATCH] blk-throttle: remove dead field last_check_time from throtl_grp
Date: Fri, 17 Jul 2026 19:25:35 +0800 [thread overview]
Message-ID: <3a711d12-5184-45b0-a4d5-2d02a17d8b3b@gmail.com> (raw)
In-Reply-To: <20260717054855.2018578-1-cui.tao@linux.dev>
On 17/7/26 1:48 pm, Tao Cui wrote:
> From: Tao Cui <cuitao@kylinos.cn>
>
> The last_check_time field in throtl_grp was used by the
> CONFIG_BLK_DEV_THROTTLING_LOW mechanism (in throtl_upgrade_check() and
> the downgrade logic) to timestamp the last upgrade/downgrade check.
>
> Commit bf20ab538c81 ("blk-throttle: remove CONFIG_BLK_DEV_THROTTLING_LOW")
> removed all five of its uses in blk-throttle.c and the surrounding LOW
> fields (latency_target, last_finish_time, checked_last_finish_time,
> avg_idletime, idletime_threshold, bio_cnt, bad_bio_cnt,
> bio_cnt_reset_time), but missed the field definition itself.
>
> It has been a dead field since then: zero references in blk-throttle.c
> and the whole tree. Remove it.
>
> Signed-off-by: Tao Cui <cuitao@kylinos.cn>
> ---
> block/blk-throttle.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/block/blk-throttle.h b/block/blk-throttle.h
> index 9d7a42c039a1..1b5775771e07 100644
> --- a/block/blk-throttle.h
> +++ b/block/blk-throttle.h
> @@ -120,8 +120,6 @@ struct throtl_grp {
> int64_t bytes_disp[2];
> int io_disp[2];
>
> - unsigned long last_check_time;
> -
> /* When did we start a new slice */
> unsigned long slice_start[2];
> unsigned long slice_end[2];
Reviewed-by: Tang Yizhou <yizhou.tang@shopee.com>
--
Best Regards,
Yi
prev parent reply other threads:[~2026-07-17 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 5:48 Tao Cui
2026-07-17 11:25 ` Tang Yizhou [this message]
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=3a711d12-5184-45b0-a4d5-2d02a17d8b3b@gmail.com \
--to=tangyeechou@gmail.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--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