From: Khazhismel Kumykov <khazhy@chromium.org>
To: Tejun Heo <tj@kernel.org>, Josef Bacik <josef@toxicpanda.com>,
Jens Axboe <axboe@kernel.dk>
Cc: cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
Khazhismel Kumykov <khazhy@google.com>
Subject: [PATCH v2 0/3] block/blk-throttle: Fix throttle slice time for SSDs
Date: Fri, 14 Nov 2025 15:54:31 -0800 [thread overview]
Message-ID: <20251114235434.2168072-1-khazhy@google.com> (raw)
Since commit bf20ab538c81 ("blk-throttle: remove CONFIG_BLK_DEV_THROTTLING_LOW"),
the throttle slice time differs between SSD and non-SSD devices. This
causes test failures with slow throttle speeds on SSD devices.
The first patch in the series fixes the problem by restoring the throttle
slice time to a fixed value, matching behavior seen prior to above
mentioned revert. The remaining patches clean up unneeeded code after removing
CONFIG_BLK_DEV_THROTTLING_LOW.
Guenter Roeck (3):
block/blk-throttle: Fix throttle slice time for SSDs
block/blk-throttle: drop unneeded blk_stat_enable_accounting
block/blk-throttle: Remove throtl_slice from struct throtl_data
block/blk-throttle.c | 45 ++++++++++++++------------------------------
1 file changed, 14 insertions(+), 31 deletions(-)
--
v2: block accounting fix into separate patch
2.52.0.rc1.455.g30608eb744-goog
next reply other threads:[~2025-11-14 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 23:54 Khazhismel Kumykov [this message]
2025-11-14 23:54 ` [PATCH v2 1/3] " Khazhismel Kumykov
2025-11-15 15:51 ` Yu Kuai
2025-11-14 23:54 ` [PATCH v2 2/3] block/blk-throttle: drop unneeded blk_stat_enable_accounting Khazhismel Kumykov
2025-11-15 15:53 ` Yu Kuai
2025-11-14 23:54 ` [PATCH v2 3/3] block/blk-throttle: Remove throtl_slice from struct throtl_data Khazhismel Kumykov
2025-11-15 15:56 ` Yu Kuai
2025-11-17 16:42 ` [PATCH v2 0/3] block/blk-throttle: Fix throttle slice time for SSDs Jens Axboe
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=20251114235434.2168072-1-khazhy@google.com \
--to=khazhy@chromium.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=khazhy@google.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
all inboxes | Powered by JetHome®