From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
damon@lists.linux.dev, kernel-team@meta.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/5] mm/damon: decouple sysfs from core
Date: Sun, 22 Jun 2025 14:37:54 -0700 [thread overview]
Message-ID: <20250622213759.50930-1-sj@kernel.org> (raw)
DAMON sysfs interface is coupled with core layer. It maintains some of
its keywords arrays be synchronized with matching DAMON core API enums.
It is unnecessary coupling that makes separated changes for different
layers difficult. Decouple the layers by introducing new data structure
for the mappings on DAMON sysfs interface.
SeongJae Park (5):
mm/damon/sysfs-schemes: decouple from damos_quota_goal_metric
mm/damon/sysfs-schemes: decouple from damos_action
mm/damon/sysfs-schemes: decouple from damos_wmark_metric
mm/damon/sysfs-schemes: decouple from damos_filter_type
mm/damon/sysfs: decouple from damon_ops_id
mm/damon/sysfs-schemes.c | 251 +++++++++++++++++++++++++++++----------
mm/damon/sysfs.c | 56 ++++++---
2 files changed, 232 insertions(+), 75 deletions(-)
base-commit: fbbe5fa9805364a5d354e7b0fdf0a60c67bdea01
--
2.39.5
next reply other threads:[~2025-06-22 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 21:37 SeongJae Park [this message]
2025-06-22 21:37 ` [PATCH 1/5] mm/damon/sysfs-schemes: decouple from damos_quota_goal_metric SeongJae Park
2025-06-22 21:37 ` [PATCH 2/5] mm/damon/sysfs-schemes: decouple from damos_action SeongJae Park
2025-06-22 21:37 ` [PATCH 3/5] mm/damon/sysfs-schemes: decouple from damos_wmark_metric SeongJae Park
2025-06-22 21:37 ` [PATCH 4/5] mm/damon/sysfs-schemes: decouple from damos_filter_type SeongJae Park
2025-06-22 21:37 ` [PATCH 5/5] mm/damon/sysfs: decouple from damon_ops_id 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=20250622213759.50930-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