From: SJ Park <sj@kernel.org>
Cc: SJ 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 0/6] mm/damon: update probe hits for runtime parameter commits
Date: Mon, 6 Jul 2026 21:38:20 -0700 [thread overview]
Message-ID: <20260707043828.97900-1-sj@kernel.org> (raw)
DAMON users can update DAMON parameters such as sampling and aggregation
intervals at runtime. For such changes, monitoring results that depend
on the intervals should be properly updated for better accuracy. For
example, the access frequency counter (nr_accesses) is updated. The
data attribute monitoring counter (probe_hits) is not being updated,
though. Do the updates for new parameters.
Patches Sequence
================
Patches 1-4 rename functions that are being used for nr_accesses update,
to be able to be used for probe_hits without confusion. Patch 5 does
the probe_hits update. Patch 6 update damon_probe_hits_mvsum() to cover
a corner case from the update for better accuracy.
SJ Park (6):
mm/damon/core: s/damon_max_nr_accesses()/damon_nr_samples_per_aggr()/
mm/damon/core: s/accesses_bp_to_nr_accesses/sample_bp_to_count/
mm/damon/core: s/nr_accesses_to_accesses_bp/sample_count_to_bp/
mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/
mm/damon/core: update probe hits for new parameter commit
mm/damon/core: handle unreset probe_hits in probe_hits_mvsum()
include/linux/damon.h | 10 +++---
mm/damon/core.c | 64 ++++++++++++++++++++++++-------------
mm/damon/lru_sort.c | 2 +-
mm/damon/ops-common.c | 2 +-
mm/damon/tests/core-kunit.h | 21 ++++++++----
5 files changed, 63 insertions(+), 36 deletions(-)
base-commit: 9765c7b820c4f11a416d8bc9d402e1914138f64c
--
2.47.3
next reply other threads:[~2026-07-07 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 4:38 SJ Park [this message]
2026-07-07 4:38 ` [RFC PATCH 1/6] mm/damon/core: s/damon_max_nr_accesses()/damon_nr_samples_per_aggr()/ SJ Park
2026-07-07 4:38 ` [RFC PATCH 2/6] mm/damon/core: s/accesses_bp_to_nr_accesses/sample_bp_to_count/ SJ Park
2026-07-07 4:38 ` [RFC PATCH 3/6] mm/damon/core: s/nr_accesses_to_accesses_bp/sample_count_to_bp/ SJ Park
2026-07-07 4:38 ` [RFC PATCH 4/6] mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/ SJ Park
2026-07-07 4:38 ` [RFC PATCH 5/6] mm/damon/core: update probe hits for new parameter commit SJ Park
2026-07-07 4:38 ` [RFC PATCH 6/6] mm/damon/core: handle unreset probe_hits in probe_hits_mvsum() SJ 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=20260707043828.97900-1-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