[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250512182716.50245-1-sj@kernel.org>
Date: Mon, 12 May 2025 11:27:14 -0700
From: SeongJae Park <sj@...nel.org>
To:
Cc: SeongJae Park <sj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
damon@...ts.linux.dev,
kernel-team@...a.com,
linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: [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
--
2.39.5
Powered by blists - more mailing lists