[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZnPQtJE8VqgPjaLA@infradead.org>
Date: Wed, 19 Jun 2024 23:48:20 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Yu Kuai <yukuai1@...weicloud.com>
Cc: Christoph Hellwig <hch@...radead.org>, axboe@...nel.dk, tj@...nel.org,
gregkh@...uxfoundation.org, bvanassche@....org,
josef@...icpanda.com, lizefan.x@...edance.com, hannes@...xchg.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
cgroups@...r.kernel.org, yi.zhang@...wei.com, yangerkun@...wei.com,
"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: [PATCH RFC v2 3/7] block: export some API
On Tue, Jun 18, 2024 at 03:58:54PM +0800, Yu Kuai wrote:
> There is already bigger helper blkg_conf_prep() exported, as used by bfq
> for a long time already, and this helper is introduced for code
> optimization, as iocost configuration doesn't need to access the blkg.
>
> Perhaps this should be another discussion about "design mistakes",
> however, I'm not sure why. :( Do you have previous discussions?
blkg_conf_prep at least has some level of abstraction.
But at least my conclusion is: don't make blk-iocost modular. It's
far too messy to split out, and not really worth it.
Powered by blists - more mailing lists