Re: [PATCH RFC -next 0/7] blk-iocost: support to build iocost as kernel module

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

 



Hi,

在 2024/06/13 13:54, Greg KH 写道:
On Thu, Jun 13, 2024 at 09:49:30AM +0800, Yu Kuai wrote:
From: Yu Kuai <yukuai3@xxxxxxxxxx>

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.

Yes, we discussed this before and this is actually an general question.
Main advantages are:

- Flexibility and Maintainability, allows for dynamic loading and
unloading of modules at runtime without the need to recompile and
restart the kernel, for example fixing iocost CVE in our production
environment.

- Kernel Size and Resource Usage, modules are loaded only when their
specific functionality is required.

Thanks,
Kuai


Why do this at all?

thanks,

greg k-h

.






[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [Monitors]

  Powered by Linux