[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ba735734-cffe-18a9-8bb5-03f47c3c8018@huawei.com>
Date: Thu, 24 Nov 2022 21:02:03 +0800
From: Kemeng Shi <shikemeng@...wei.com>
To: Tejun Heo <tj@...nel.org>
CC: <josef@...icpanda.com>, <axboe@...nel.dk>,
<cgroups@...r.kernel.org>, <linux-block@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 11/11] blk-throttle: Use more siutable time_after check
for update slice_start
on 11/24/2022 2:29 AM, Tejun Heo wrote:
> On Wed, Nov 23, 2022 at 02:04:01PM +0800, Kemeng Shi wrote:
>> Use more siutable time_after check for update slice_start
>
> Why is it more suitable?
There is no need to assign tg->slice_start[rw] to start when they are
equal already. So time_after seems more suitable here.
--
Best wishes
Kemeng Shi
Powered by blists - more mailing lists