[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <unns4jtkiqdde3v7hzmd4yi2y7ylh4fh545dsn3imytgbg4x72@iq3mwwemygh5>
Date: Wed, 17 Apr 2024 12:25:42 +0200
From: Michal Koutný <mkoutny@...e.com>
To: Yu Kuai <yukuai1@...weicloud.com>
Cc: axboe@...nel.dk, chenhuacai@...nel.org, tj@...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: Re: [PATCH RFC v2 0/6] blk-throttle: support enable and disable
during runtime
On Wed, Apr 17, 2024 at 09:09:07AM +0800, Yu Kuai <yukuai1@...weicloud.com> wrote:
> Yes, bfq already support that,
I've never noticed CONFIG_IOSCHED_BFQ is a tristate that explains (me) a
lot. Thanks!
> First of all, users can only load these policies when they need, and
> reduce kernel size; Then, when these policies is not loaded, IO fast
> path will be slightly shorter, and save some memory overhead for each
> disk.
..and there is no new complexity thanks to the above.
(I'm only catching up with subthread of patch 5/6.)
It seems the old complexity could be simplified by the way of lazy
inits. Intereseting...
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists