RFC mm/damon: build-enable essential DAMON components by default
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm/damon/Kconfig: defaults VADDR, PADDR, and SYSFS to DAMONmm/ | +3 | 0 replies | |
| 2/2 | mm/damon/Kconfig: enable CONFIG_DAMON by defaultmm/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/2] mm/damon: build-enable essential DAMON components by default
As of this writing, a few major distros including Alma, Amazon, Android, CentOS, Debian, Fedora, and Oracle are build-enabling DAMON (set CONFIG_DAMON[1]). Configuring DAMON is not very easy, since it is disabled by default, and there are multiple essential options that need to be manually turned on, one by one. Make it easier, by grouping essential configurations to be enabled with one selection, and enabling build of the essential parts of DAMON by default.
Note that build-enabling DAMON does not introduce a real risk, since it makes no behavioral change by default. It requires users to make explicit requests to do something. Only one potential risk is making the size of the kernel a little bit larger. On a configuration, it increases the resulting kernel package binary size by 337,685 bytes, which is about 0.1 % of the final package file.
[1] https://oracle.github.io/kconfigs/?config=UTS_RELEASE&config=DAMON
SeongJae Park (2):
mm/damon/Kconfig: defaults VADDR, PADDR, and SYSFS to DAMON mm/damon/Kconfig: enable CONFIG_DAMON by default
mm/damon/Kconfig | 4 ++++ 1 file changed, 4 insertions(+)
base-commit: 399b2f61ec1add307a04f0d128a3de333c4d1daf
Signature · 1 line
2.39.5