[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024061342-walk-cavalier-7e48@gregkh>
Date: Thu, 13 Jun 2024 07:54:03 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Yu Kuai <yukuai1@...weicloud.com>
Cc: axboe@...nel.dk, tj@...nel.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, yukuai3@...wei.com, yi.zhang@...wei.com,
yangerkun@...wei.com
Subject: Re: [PATCH RFC -next 0/7] blk-iocost: support to build iocost as
kernel module
On Thu, Jun 13, 2024 at 09:49:30AM +0800, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@...wei.com>
>
> Yu Kuai (7):
> kernfs: export pr_cont_kernfs_path()
> cgroup: export cgroup_parse_float
> block: export some API
> blk-iocost: factor out helpers to handle params from ioc_qos_write()
> blk-iocost: parse params before initializing iocost
> blk-iocost: support to free iocost
> blk-iocost: support to build iocost as kernel module
No where do you say _why_ building this as a module is a good idea.
Why do this at all?
thanks,
greg k-h
Powered by blists - more mailing lists