From: Steven Rostedt <rostedt@goodmis.org>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2 1/2] mm/damon/core: add a tracepoint for damos apply target regions
Date: Tue, 3 Oct 2023 20:50:22 -0400 [thread overview]
Message-ID: <20231003205022.58ffcb2a@gandalf.local.home> (raw)
In-Reply-To: <20230913022050.2109-2-sj@kernel.org>
On Wed, 13 Sep 2023 02:20:49 +0000
SeongJae Park <sj@kernel.org> wrote:
> DAMON provides damon_aggregated tracepoint, which exposes details of
> each region and its access monitoring results. It is useful for
> getting whole monitoring results, e.g., for recording purposes.
>
> For investigations of DAMOS, DAMON Sysfs interface provides DAMOS
> statistics and tried_regions directory. But, those provides only
> statistics and snapshots. If the scheme is frequently applied and if
> the user needs to know every detail of DAMOS behavior, the
> snapshot-based interface could be insufficient and expensive.
>
> As a last resort, userspace users need to record the all monitoring
> results via damon_aggregated tracepoint and simulate how DAMOS would
> worked. It is unnecessarily complicated. DAMON kernel API users,
> meanwhile, can do that easily via before_damos_apply() callback field of
> 'struct damon_callback', though.
>
> Add a tracepoint that will be called just after before_damos_apply()
> callback for more convenient investigations of DAMOS. The tracepoint
> exposes all details about each regions, similar to damon_aggregated
> tracepoint.
>
> Please note that DAMOS is currently not only for memory management but
> also for query-like efficient monitoring results retrievals (when 'stat'
> action is used). Until now, only statistics or snapshots were
> supported. Addition of this tracepoint allows efficient full recording
> of DAMOS-based filtered monitoring results.
>
From a tracing point of view.
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2023-10-04 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 2:20 [PATCH RESEND v2 0/2] mm/damon: " SeongJae Park
2023-09-13 2:20 ` [PATCH RESEND v2 1/2] mm/damon/core: " SeongJae Park
2023-10-04 0:50 ` Steven Rostedt [this message]
2023-09-13 2:20 ` [PATCH RESEND v2 2/2] Docs/admin-guide/mm/damon/usage: document damos_before_apply tracepoint 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=20231003205022.58ffcb2a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=sj@kernel.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