From: "Yu Kuai" <yukuai@fnnas.com>
To: "Khazhismel Kumykov" <khazhy@chromium.org>,
"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>,
"Guenter Roeck" <linux@roeck-us.net>,
"Yu Kuai" <yukuai@kernel.org>,
"Khazhismel Kumykov" <khazhy@google.com>
Subject: Re: [PATCH v2 1/3] block/blk-throttle: Fix throttle slice time for SSDs
Date: Sat, 15 Nov 2025 23:51:27 +0800 [thread overview]
Message-ID: <2d827b93-9ffa-4767-8409-88460e64a407@fnnas.com> (raw)
In-Reply-To: <20251114235434.2168072-2-khazhy@google.com>
在 2025/11/15 7:54, Khazhismel Kumykov 写道:
> From: Guenter Roeck<linux@roeck-us.net>
>
> Commit d61fcfa4bb18 ("blk-throttle: choose a small throtl_slice for SSD")
> introduced device type specific throttle slices if BLK_DEV_THROTTLING_LOW
> was enabled. Commit bf20ab538c81 ("blk-throttle: remove
> CONFIG_BLK_DEV_THROTTLING_LOW") removed support for BLK_DEV_THROTTLING_LOW,
> but left the device type specific throttle slices in place. This
> effectively changed throttling behavior on systems with SSD which now use
> a different and non-configurable slice time compared to non-SSD devices.
> Practical impact is that throughput tests with low configured throttle
> values (65536 bps) experience less than expected throughput on SSDs,
> presumably due to rounding errors associated with the small throttle slice
> time used for those devices. The same tests pass when setting the throttle
> values to 65536 * 4 = 262144 bps.
>
> The original code sets the throttle slice time to DFL_THROTL_SLICE_HD if
> CONFIG_BLK_DEV_THROTTLING_LOW is disabled. Restore that code to fix the
> problem. With that, DFL_THROTL_SLICE_SSD is no longer necessary. Revert to
> the original code and re-introduce DFL_THROTL_SLICE to replace both
> DFL_THROTL_SLICE_HD and DFL_THROTL_SLICE_SSD. This effectively reverts
> commit d61fcfa4bb18 ("blk-throttle: choose a small throtl_slice for SSD").
>
> While at it, also remove MAX_THROTL_SLICE since it is not used anymore.
>
> Fixes: bf20ab538c81 ("blk-throttle: remove CONFIG_BLK_DEV_THROTTLING_LOW")
> Cc: Yu Kuai<yukuai@kernel.org>
> Cc: Tejun Heo<tj@kernel.org>
> Signed-off-by: Guenter Roeck<linux@roeck-us.net>
> Signed-off-by: Khazhismel Kumykov<khazhy@google.com>
> ---
> block/blk-throttle.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
LGTM
Reviewed-by: Yu Kuai <yukuai@fnnas.com>
--
Thanks
Kuai
next prev parent reply other threads:[~2025-11-15 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 23:54 [PATCH v2 0/3] block/blk-throttle: Fix throttle slice time for SSDs Khazhismel Kumykov
2025-11-14 23:54 ` [PATCH v2 1/3] " Khazhismel Kumykov
2025-11-15 15:51 ` Yu Kuai [this message]
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=2d827b93-9ffa-4767-8409-88460e64a407@fnnas.com \
--to=yukuai@fnnas.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=khazhy@chromium.org \
--cc=khazhy@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=tj@kernel.org \
--cc=yukuai@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