From: Kunwu Chan <kunwu.chan@gmail.com>
To: Ravi Jonnalagadda <ravis.opensrc@gmail.com>
Cc: Kunwu Chan <kunwu.chan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
SJ Park <sj@kernel.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Bijan Tabatabai <bijan311@gmail.com>,
Ajay Joshi <ajayjoshi@micron.com>,
Honggyu Kim <honggyu.kim@sk.com>,
Yunjeong Mun <yunjeong.mun@sk.com>,
Akinobu Mita <akinobu.mita@gmail.com>,
Lian Wang <lianux.mm@gmail.com>,
Kunwu Chan <kunwu.chan@linux.dev>
Subject: Re: [PATCH] mm/damon: add damos_node_eligible_mem_bp tracepoint
Date: Mon, 5 Oct 2026 18:04:29 +0800 [thread overview]
Message-ID: <20261005100435.1211485-1-kunwu.chan@gmail.com> (raw)
In-Reply-To: <20261003202727.3673-1-ravis.opensrc@gmail.com>
Hi Ravi,
I agree with SJ that this would be more useful as a general quota-goal
tracepoint rather than being specific to NODE_ELIGIBLE_MEM_BP. The
target_value and current_value fields are not metric-specific.
On Sat, 3 Oct 2026 13:27:27 -0700 Ravi Jonnalagadda <ravis.opensrc@gmail.com> wrote:
> Add a tracepoint for DAMOS_QUOTA_NODE_ELIGIBLE_MEM_BP quota goal
> evaluation. The tracepoint fires once per quota-score computation when
> the goal metric is DAMOS_QUOTA_NODE_ELIGIBLE_MEM_BP, exposing
> context_idx, scheme_idx, nid, target_value, and current_value.
> current_value is reported as the quota tuning sees it, after the goal's
> complement setting is applied.
>
> The DAMOS_QUOTA_NODE_ELIGIBLE_MEM_BP metric expresses node memory
> occupancy as basis points of eligible bytes. This information is not
> exposed through any existing external interface (perf stat, /proc, or
> sysfs), so the tracepoint is the only way for userspace to observe the
> target and current eligible-memory basis point values at quota-scoring
> time.
>
> Link: https://lore.kernel.org/linux-mm/20260428030520.701-1-ravis.opensrc@gmail.com/
> Signed-off-by: Ravi Jonnalagadda <ravis.opensrc@gmail.com>
> ---
> include/trace/events/damon.h | 31 +++++++++++++++++++++++++++++++
> mm/damon/core.c | 16 ++++++++++++++++
> 2 files changed, 47 insertions(+)
>
> diff --git a/include/trace/events/damon.h b/include/trace/events/damon.h
> index 8851727ae162..2c7249cc7c88 100644
> --- a/include/trace/events/damon.h
> +++ b/include/trace/events/damon.h
> @@ -74,6 +74,37 @@ TRACE_EVENT(damos_esz,
> __entry->esz)
> );
>
> +/* Per-tick DAMOS_QUOTA_NODE_ELIGIBLE_MEM_BP goal evaluation. */
The comment says "Per-tick", but the event is emitted for each matching
goal in damos_quota_score(). "Per quota-goal evaluation" would be more
precise.
> +TRACE_EVENT(damos_node_eligible_mem_bp,
> +
> + TP_PROTO(unsigned int context_idx, unsigned int scheme_idx,
> + int nid,
> + unsigned long target_value, unsigned long current_value),
> +
> + TP_ARGS(context_idx, scheme_idx, nid, target_value, current_value),
> +
> + TP_STRUCT__entry(
> + __field(unsigned int, context_idx)
> + __field(unsigned int, scheme_idx)
> + __field(int, nid)
> + __field(unsigned long, target_value)
> + __field(unsigned long, current_value)
Also, context_idx is currently always 0 here, since
damos_quota_score() only has struct damon_ctx * and no context index.
If this tracepoint is generalized, it may be worth considering how the
context/scheme are identified rather than introducing another tracepoint
field that is currently always 0.
Thanks,
Kunwu
> + ),
> +
> + TP_fast_assign(
> + __entry->context_idx = context_idx;
> + __entry->scheme_idx = scheme_idx;
> + __entry->nid = nid;
> + __entry->target_value = target_value;
> + __entry->current_value = current_value;
> + ),
> +
> + TP_printk("ctx_idx=%u scheme_idx=%u nid=%d target_value=%lu current_value=%lu",
> + __entry->context_idx, __entry->scheme_idx,
> + __entry->nid,
> + __entry->target_value, __entry->current_value)
> +);
> +
> TRACE_EVENT_CONDITION(damos_before_apply,
>
> TP_PROTO(unsigned int context_idx, unsigned int scheme_idx,
> diff --git a/mm/damon/core.c b/mm/damon/core.c
> index b63e60ef8990..6ddd15dc4f55 100644
> --- a/mm/damon/core.c
> +++ b/mm/damon/core.c
> @@ -3294,6 +3294,22 @@ static unsigned long damos_quota_score(struct damon_ctx *c, struct damos *s)
> highest_score = max(highest_score,
> mult_frac(goal->current_value, 10000,
> goal->target_value));
> +
> + if (goal->metric == DAMOS_QUOTA_NODE_ELIGIBLE_MEM_BP &&
> + trace_damos_node_eligible_mem_bp_enabled()) {
> + unsigned int cidx = 0, sidx = 0;
> + struct damos *siter;
> +
> + damon_for_each_scheme(siter, c) {
> + if (siter == s)
> + break;
> + sidx++;
> + }
> + trace_damos_node_eligible_mem_bp(cidx, sidx,
> + goal->nid,
> + goal->target_value,
> + goal->current_value);
> + }
> }
>
> return highest_score;
>
> base-commit: 763ad0211c7b587344f03bc4d1299810aeb736f4
> --
> 2.54.0 (Apple Git-157)
>
>
Sent using hkml (https://github.com/sjp38/hackermail)
prev parent reply other threads:[~2026-10-05 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 20:27 Ravi Jonnalagadda
2026-10-04 8:01 ` SJ Park
2026-10-04 9:16 ` Steven Rostedt
2026-10-05 10:04 ` Kunwu Chan [this message]
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=20261005100435.1211485-1-kunwu.chan@gmail.com \
--to=kunwu.chan@gmail.com \
--cc=ajayjoshi@micron.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bijan311@gmail.com \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=honggyu.kim@sk.com \
--cc=kunwu.chan@linux.dev \
--cc=lianux.mm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=ravis.opensrc@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sj@kernel.org \
--cc=yunjeong.mun@sk.com \
/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
all inboxes | Powered by JetHome®