From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 0/7] mm/damon: update probe hits for runtime parameter commits
Date: Wed, 8 Jul 2026 07:34:40 -0700 [thread overview]
Message-ID: <20260708143441.124565-1-sj@kernel.org> (raw)
In-Reply-To: <20260708135359.122587-1-sj@kernel.org>
On Wed, 8 Jul 2026 06:53:50 -0700 SJ Park <sj@kernel.org> wrote:
> 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.
Sashiko found no blocker but a wrong function name [1] on the commit message of
patch 1. In short, need s/nr_samples_per_aggr/max_nr_accesses/ for the commit
message. Please read my reply [1] for more detail.
Andrew, as it is a relatively small change on commit message, could you make
the fix when you pick the patch up? If you prefer v2, please feel free to let
me know.
[1] https://lore.kerrnel.org/20260708143130.124419-1-sj@kernel.org
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-07-08 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 13:53 [PATCH 0/7] mm/damon: update probe hits for runtime parameter commits SJ Park
2026-07-08 13:53 ` [PATCH 1/7] mm/damon/core: remove comment and test for nr_to_bp() divide-by-zero SJ Park
2026-07-08 14:13 ` sashiko-bot
2026-07-08 14:25 ` SJ Park
2026-07-08 14:31 ` SJ Park
2026-07-08 13:53 ` [PATCH 2/7] mm/damon/core: s/damon_max_nr_accesses()/damon_nr_samples_per_aggr()/ SJ Park
2026-07-08 13:53 ` [PATCH 3/7] mm/damon/core: s/accesses_bp_to_nr_accesses/sample_bp_to_count/ SJ Park
2026-07-08 13:53 ` [PATCH 4/7] mm/damon/core: s/nr_accesses_to_accesses_bp/sample_count_to_bp/ SJ Park
2026-07-08 14:03 ` sashiko-bot
2026-07-08 14:26 ` SJ Park
2026-07-08 13:53 ` [PATCH 5/7] mm/damon/core: s/nr_accesses_for_new_attrs/nr_samples_for_new_attrs/ SJ Park
2026-07-08 14:09 ` sashiko-bot
2026-07-08 14:27 ` SJ Park
2026-07-08 13:53 ` [PATCH 6/7] mm/damon/core: update probe hits for new parameter commit SJ Park
2026-07-08 14:08 ` sashiko-bot
2026-07-08 14:28 ` SJ Park
2026-07-08 13:53 ` [PATCH 7/7] mm/damon/core: handle unreset probe_hits in probe_hits_mvsum() SJ Park
2026-07-08 14:34 ` SJ Park [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=20260708143441.124565-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.