From: SeongJae Park <sj@kernel.org>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, kernel-team@meta.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [RFC PATCH 0/2] mm/damon: build-enable essential DAMON components by default
Date: Mon, 12 May 2025 11:27:14 -0700 [thread overview]
Message-ID: <20250512182716.50245-1-sj@kernel.org> (raw)
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
next reply other threads:[~2025-05-12 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 18:27 SeongJae Park [this message]
2025-05-12 18:27 ` [RFC PATCH 1/2] mm/damon/Kconfig: defaults VADDR, PADDR, and SYSFS to DAMON SeongJae Park
2025-05-12 18:27 ` [RFC PATCH 2/2] mm/damon/Kconfig: enable CONFIG_DAMON by default SeongJae Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250512182716.50245-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox