From: SeongJae Park <sj@kernel.org>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [RFC PATCH 1/2] mm/damon/stat: add a parameter for reading kdamond pid
Date: Mon, 13 Apr 2026 21:49:59 -0700 [thread overview]
Message-ID: <20260414045002.88110-2-sj@kernel.org> (raw)
In-Reply-To: <20260414045002.88110-1-sj@kernel.org>
Knowing the pid of the kdamonds can help user-space management including
monitoring of DAMON's system resource consumption. To make it easier,
DAMON_SYSFS, DAMON_RECLAIM and DAMON_LRU_SORT provide the pid
information. DAMON_STAT is not providing it, though. Expose the pid of
DAMON_STAT kdamond via a new read-only module parameter, namely
kdamond_pid. This also makes DAMON modules usage more standardized,
because DAMON_RECLAIM and DAMON_LRU_SORT also provide the information
via their read-only parameters of the same name.
Signed-off-by: SeongJae Park <sj@kernel.org>
---
mm/damon/stat.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/mm/damon/stat.c b/mm/damon/stat.c
index 99ba346f9e325..21fa04d95eeac 100644
--- a/mm/damon/stat.c
+++ b/mm/damon/stat.c
@@ -44,6 +44,15 @@ module_param(aggr_interval_us, ulong, 0400);
MODULE_PARM_DESC(aggr_interval_us,
"Current tuned aggregation interval in microseconds");
+/*
+ * PID of the DAMON thread
+ *
+ * If DAMON_STAT is enabled, this becomes the PID of the worker thread.
+ * Else, -1.
+ */
+static int kdamond_pid __read_mostly = -1;
+module_param(kdamond_pid, int, 0400);
+
static struct damon_ctx *damon_stat_context;
static unsigned long damon_stat_last_refresh_jiffies;
@@ -260,6 +269,9 @@ static int damon_stat_start(void)
damon_stat_context = NULL;
return err;
}
+ kdamond_pid = damon_kdamond_pid(damon_stat_context);
+ if (kdamond_pid < 0)
+ return kdamond_pid;
damon_stat_last_refresh_jiffies = jiffies;
call_control.data = damon_stat_context;
@@ -269,6 +281,7 @@ static int damon_stat_start(void)
static void damon_stat_stop(void)
{
damon_stop(&damon_stat_context, 1);
+ kdamond_pid = -1;
damon_destroy_ctx(damon_stat_context);
damon_stat_context = NULL;
}
--
2.47.3
next prev parent reply other threads:[~2026-04-14 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 4:49 [RFC PATCH 0/2] mm/damon/stat: add kdamond_pid parameter SeongJae Park
2026-04-14 4:49 ` SeongJae Park [this message]
2026-04-14 5:37 ` (sashiko review) [RFC PATCH 1/2] mm/damon/stat: add a parameter for reading kdamond pid SeongJae Park
2026-04-14 4:50 ` [RFC PATCH 2/2] Docs/admin-guide/mm/damon/stat: document kdamond_pid parameter 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=20260414045002.88110-2-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--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