[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZO5vJ2i3qfvtBC7B@slm.duckdns.org>
Date: Tue, 29 Aug 2023 12:20:23 -1000
From: Tejun Heo <tj@...nel.org>
To: Yu Kuai <yukuai1@...weicloud.com>
Cc: josef@...icpanda.com, axboe@...nel.dk, yukuai3@...wei.com,
mkoutny@...e.com, cgroups@...r.kernel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
yi.zhang@...wei.com, yangerkun@...wei.com
Subject: Re: [PATCH -next v2 4/4] blk-throttle: consider
'carryover_ios/bytes' in throtl_trim_slice()
On Wed, Aug 16, 2023 at 09:27:08AM +0800, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@...wei.com>
>
> Currently, 'carryover_ios/bytes' is not handled in throtl_trim_slice(),
> for consequence, 'carryover_ios/bytes' will be used to throttle bio
> multiple times, for example:
>
> 1) set iops limit to 100, and slice start is 0, slice end is 100ms;
> 2) current time is 0, and 10 ios are dispatched, those io won't be
> throttled and io_disp is 10;
> 3) still at current time 0, update iops limit to 1000, carryover_ios is
> updated to (0 - 10) = -10;
> 4) in this slice(0 - 100ms), io_allowed = 100 + (-10) = 90, which means
> only 90 ios can be dispatched without waiting;
> 5) assume that io is throttled in slice(0 - 100ms), and
> throtl_trim_slice() update silce to (100ms - 200ms). In this case,
> 'carryover_ios/bytes' is not cleared and still only 90 ios can be
> dispatched between 100ms - 200ms.
>
> Fix this problem by updating 'carryover_ios/bytes' in
> throtl_trim_slice().
>
> Fixes: a880ae93e5b5 ("blk-throttle: fix io hung due to configuration updates")
> Reported-by: zhuxiaohui <zhuxiaohui.400@...edance.com>
> Link: https://lore.kernel.org/all/20230812072116.42321-1-zhuxiaohui.400@bytedance.com/
> Signed-off-by: Yu Kuai <yukuai3@...wei.com>
Acked-by: Tejun Heo <tj@...nel.org>
Thanks.
--
tejun
Powered by blists - more mailing lists