Re: [PATCH 11/11] blk-throttle: Use more siutable time_after check for update slice_start

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Kemeng Shi <shikemeng@xxxxxxxxxx>
Subject: Re: [PATCH 11/11] blk-throttle: Use more siutable time_after check for update slice_start
From: Tejun Heo <tj@xxxxxxxxxx>
Date: Wed, 23 Nov 2022 08:29:49 -1000
Cc: josef@xxxxxxxxxxxxxx, axboe@xxxxxxxxx, cgroups@xxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20221123060401.20392-12-shikemeng@huawei.com>
References: <20221123060401.20392-1-shikemeng@huawei.com> <20221123060401.20392-12-shikemeng@huawei.com>

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?

-- 
tejun

Follow-Ups:
- Re: [PATCH 11/11] blk-throttle: Use more siutable time_after check for update slice_start
  - From: Kemeng Shi

References:
- [PATCH 00/11] A few bugfix and cleanup patches for blk-throttle
  - From: Kemeng Shi
- [PATCH 11/11] blk-throttle: Use more siutable time_after check for update slice_start
  - From: Kemeng Shi

Prev by Date: Re: [PATCH 10/11] blk-throttle: remove unused variable td in tg_update_has_rules
Next by Date: Re: [PATCH 09/11] blk-throttle: remove unnecessary check for validation of limit index
Previous by thread: [PATCH 11/11] blk-throttle: Use more siutable time_after check for update slice_start
Next by thread: Re: [PATCH 11/11] blk-throttle: Use more siutable time_after check for update slice_start
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux