From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, kernel-team@meta.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/2] mm/damon/stat: expose auto-tuned intervals and non-idle ages
Date: Thu, 11 Sep 2025 19:06:19 -0700 [thread overview]
Message-ID: <20250912020619.59642-1-sj@kernel.org> (raw)
In-Reply-To: <20250910040022.168223-1-sj@kernel.org>
On Tue, 9 Sep 2025 21:00:20 -0700 SeongJae Park <sj@kernel.org> wrote:
> DAMON_STAT is intentionally providing limited information for easy
> consumption. 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 it 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
> impossible.
>
> To overcome the limitations, expose the auto-tuned aggregation interval
> with a new parameter named xxx and the age of non-zero nr_accesses
s/xx/aggr_interval_us/
Forgot updating that before posting, sorry. The next version should fix it.
Thanks,
SJ
[...]
prev parent reply other threads:[~2025-09-12 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 4:00 SeongJae Park
2025-09-10 4:00 ` [RFC PATCH 1/2] mm/damon/stat: expose the current tuned aggregation interval SeongJae Park
2025-09-10 4:00 ` [RFC PATCH 2/2] mm/damon/stat: expose negative idle time SeongJae Park
2025-09-12 2:06 ` SeongJae 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=20250912020619.59642-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox