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/2] mm/damon/stat: expose auto-tuned intervals and non-idle ages
Date: Tue, 16 Sep 2025 11:31:25 -0700 [thread overview]
Message-ID: <20250916183127.65708-1-sj@kernel.org> (raw)
DAMON_STAT is intentionally providing limited information for easy
consumption of the information. From production fleet level usages,
below limitations are found, though.
The aggregation interval of DAMON_STAT represents the granularity of the
memory_idle_ms_percentiles. But the interval is auto-tuned and not
exposed to users, so users cannot know the granularity.
All memory regions of non-zero (positive) nr_accesses are treated as
having zero idle time. A significant portion of production systems have
such zero idle time. Hence breakdown of warm and hot data is nearly
impossible.
Make following changes to overcome the limitations. Expose the
auto-tuned aggregation interval with a new parameter named
aggr_interval_us. Expose the age of non-zero nr_accesses (how long >0
access frequency the region retained) regions as a negative idle time.
Changes from RFC
(https://lore.kernel.org/20250910040022.168223-1-sj@kernel.org)
- Rebase on latest mm-new
- Wordsmith commit messages
SeongJae Park (2):
mm/damon/stat: expose the current tuned aggregation interval
mm/damon/stat: expose negative idle time
mm/damon/stat.c | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
base-commit: ae4745146347aef91dc328d1d9a39f0643ee244d
--
2.39.5
next reply other threads:[~2025-09-16 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 18:31 SeongJae Park [this message]
2025-09-16 18:31 ` [PATCH 1/2] mm/damon/stat: expose the current tuned aggregation interval SeongJae Park
2025-09-16 18:31 ` [PATCH 2/2] mm/damon/stat: expose negative idle time 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=20250916183127.65708-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 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.