diff options
| author |   SeongJae Park <sj@kernel.org> | 2025-05-20 21:27:55 -0700 |
|---|---|---|
| committer |   Andrew Morton <akpm@linux-foundation.org> | 2025-05-31 22:46:12 -0700 |
| commit | 28615e6eed152f2fda5486680090b74aeed7b554 (patch) | |
| tree | c49d73559b6f979f7e8e37389b8aa74bdb111516 /mm | |
| parent | mm/damon/Kconfig: set DAMON_{VADDR,PADDR,SYSFS} default to DAMON (diff) | |
| download | linux-rng-28615e6eed152f2fda5486680090b74aeed7b554.tar.xz linux-rng-28615e6eed152f2fda5486680090b74aeed7b554.zip | |
mm/damon/Kconfig: enable CONFIG_DAMON by default
As of this writing, multiple major distros including Alma, Amazon,
Android, CentOS, Debian, Fedora, and Oracle are build-enabling DAMON (set
CONFIG_DAMON[1]). Enabling it by default will save configuration setup
time for the current and future DAMON users.
Build-enabling DAMON does not introduce a real risk since it makes no
behavioral change by default. It requires explicit user requests to do
anything. Only one potential risk is making the size of the kernel a
little bit larger. On a production-purpose configuration, it increases
the resulting kernel package size by about 0.1 % of the final package
file. I believe that's too small to be a real problem in common setups.
Hence, the benefit of enabling CONFIG_DAMON outweighs the potential risk.
Set CONFIG_DAMON by default.
Link: https://oracle.github.io/kconfigs/?config=UTS_RELEASE&config=DAMON [1]
Link: https://lkml.kernel.org/r/20250521042755.39653-3-sj@kernel.org
Signed-off-by: SeongJae Park <sj@kernel.org>
Acked-by: Honggyu Kim <honggyu.kim@sk.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm')
| -rw-r--r-- | mm/damon/Kconfig | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/mm/damon/Kconfig b/mm/damon/Kconfig index c93d0c56b963..551745df011b 100644 --- a/mm/damon/Kconfig +++ b/mm/damon/Kconfig @@ -4,6 +4,7 @@ menu "Data Access Monitoring" config DAMON bool "DAMON: Data Access Monitoring Framework" + default y help This builds a framework that allows kernel subsystems to monitor access frequency of each memory region. The information can be useful |