From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: "Liam R. Howlett" <liam@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Lorenzo Stoakes <ljs@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@kernel.org>,
Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
damon@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2.1 00/28] mm/damon: introduce data attributes monitoring
Date: Thu, 14 May 2026 17:41:19 -0700 [thread overview]
Message-ID: <20260515004120.128430-1-sj@kernel.org> (raw)
In-Reply-To: <20260514140904.119781-1-sj@kernel.org>
On Thu, 14 May 2026 07:08:33 -0700 SeongJae Park <sj@kernel.org> wrote:
> TL; DR
> ======
>
> Extend DAMON for monitoring general data attributes other than accesses.
> The short term motivation is lightweight page type (e.g., belonging
> cgroup) aware monitoring. In long term, this will help extending DAMON
> for multiple access events capture primitives (e.g., page faults and
> PMU) and eventually pivotting DAMON to a "Data Attributes Monitoring and
> Operations eNgine" in long term.
Sashiko failed [1] reviewing this due to a problem at finding a fresh baseline
commit. I will shortly post the next version (RFC v2.2) after rebasing to
mm-stable (7.1-rc3) for avoiding the issue.
[1] https://lore.kernel.org/20260514205555.51653-1-sj@kernel.org
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-05-15 0:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 14:08 [RFC PATCH v2.1 00/28] mm/damon: introduce data attributes monitoring SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 01/28] mm/damon/core: introduce struct damon_probe SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 02/28] mm/damon/core: embed damon_probe objects in damon_ctx SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 03/28] mm/damon/core: introduce damon_filter SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 04/28] mm/damon/core: commit probes SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 05/28] mm/damon/core: introduce damon_region->probe_hits SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 06/28] mm/damon/core: introduce damon_ops->apply_probes SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 07/28] mm/damon/core: do data attributes monitoring SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 08/28] mm/damon/paddr: support " SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 09/28] mm/damon/sysfs: implement probes dir SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 10/28] mm/damon/sysfs: implement probe dir SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 11/28] mm/damon/sysfs: implement filters directory SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 12/28] mm/damon/sysfs: implement filter dir SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 13/28] mm/damon/sysfs: implement filter dir files SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 14/28] mm/damon/sysfs: setup probes on DAMON core API parameters SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 15/28] mm/damon/sysfs-schemes: implement tried_regions/<r>/probes/ SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 16/28] mm/damon/sysfs-schemes: implement probe dir SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 17/28] mm/damon/sysfs-schemes: implement probe/hits file SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 18/28] mm/damon: trace probe_hits SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 19/28] selftests/damon/sysfs.sh: test probes dir SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 20/28] Docs/mm/damon/design: document data attributes monitoring SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 21/28] Docs/admin-guide/mm/damon/usage: " SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 22/28] mm/damon/core: introduce DAMON_FILTER_TYPE_MEMCG SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 23/28] mm/damon/paddr: support DAMON_FILTER_TYPE_MEMCG SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 24/28] mm/damon/sysfs: add filters/<F>/path file SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 25/28] mm/damon/sysfs-schemes: move memcg_path_to_id() to sysfs-common SeongJae Park
2026-05-14 14:08 ` [RFC PATCH v2.1 26/28] mm/damon/sysfs: setup damon_filter->memcg_id from path SeongJae Park
2026-05-14 14:09 ` [RFC PATCH v2.1 27/28] Docs/mm/damon/design: update for memcg damon filter SeongJae Park
2026-05-14 14:09 ` [RFC PATCH v2.1 28/28] Docs/admin-guide/mm/damon/usage: " SeongJae Park
2026-05-15 0:41 ` 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=20260515004120.128430-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@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 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.