[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9edb4ff7-0094-d2b1-28e5-70daeb8b899c@huaweicloud.com>
Date: Sat, 13 Apr 2024 09:57:24 +0800
From: Yu Kuai <yukuai1@...weicloud.com>
To: Tejun Heo <tj@...nel.org>, Yu Kuai <yukuai1@...weicloud.com>
Cc: axboe@...nel.dk, chenhuacai@...nel.org, josef@...icpanda.com,
jhs@...atatu.com, svenjoac@....de, raven@...maw.net, pctammela@...atatu.com,
qde@...cy.de, zhaotianrui@...ngson.cn, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, loongarch@...ts.linux.dev,
cgroups@...r.kernel.org, yi.zhang@...wei.com, yangerkun@...wei.com,
"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: [PATCH RFC v2 1/6] blk-throttle: remove
CONFIG_BLK_DEV_THROTTLING_LOW
Hi,
在 2024/04/13 1:30, Tejun Heo 写道:
> On Sat, Apr 06, 2024 at 04:00:54PM +0800, Yu Kuai wrote:
>> From: Yu Kuai <yukuai3@...wei.com>
>>
>> One the one hand, it's marked EXPERIMENTAL since 2017, and looks like
>> there are no users since then, and no testers and no developers, it's
>> just not active at all.
>>
>> On the other hand, even if the config is disabled, there are still many
>> fields in throtl_grp and throtl_data and many functions that are only
>> used for throtl low.
>>
>> At last, currently blk-throtl is initialized during disk initialization,
>> and destroyed during disk removal, and it exposes many functions to be
>> called directly from block layer. Hence I'm planning to optimize
>> blk-throtl and finially support building it as kernel module. Remove
>> throtl low will make the work much easier.
>>
>> Signed-off-by: Yu Kuai <yukuai3@...wei.com>
>
> Acked-by: Tejun Heo <tj@...nel.org>
>
> I haven't seen any usage but let's see if anyone complains.
Thanks for the review!
Kuai
>
> Thanks.
>
Powered by blists - more mailing lists