[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250521042755.39653-1-sj@kernel.org>
Date: Tue, 20 May 2025 21:27:53 -0700
From: SeongJae Park <sj@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: SeongJae Park <sj@...nel.org>,
damon@...ts.linux.dev,
kernel-team@...a.com,
linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: [PATCH 0/2] mm/damon: build-enable essential DAMON components 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]). 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 any 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 binary size by about 0.1 % of
the final package file. I believe that's too small to be a real problem
in common setups.
Changes from RFC
(https://lore.kernel.org/20250512182716.50245-1-sj@kernel.org)
- Rebase to latest mm-new
- Wordsmith cover letter and commit messages
[1] https://oracle.github.io/kconfigs/?config=UTS_RELEASE&config=DAMON
SeongJae Park (2):
mm/damon/Kconfig: set DAMON_{VADDR,PADDR,SYSFS} default to DAMON
mm/damon/Kconfig: enable CONFIG_DAMON by default
mm/damon/Kconfig | 4 ++++
1 file changed, 4 insertions(+)
base-commit: 88d53b68fa80a693259ba705b4750f91e9c77888
--
2.39.5
Powered by blists - more mailing lists