DAMON development mailing list
 help / color / mirror / Atom feed
From: Lian Wang <lianux.mm@gmail.com>
To: SJ Park <sj@kernel.org>
Cc: damon@lists.linux.dev,
	Ravi Jonnalagadda <ravis.opensrc@gmail.com>,
	Akinobu Mita <akinobu.mita@gmail.com>,
	Andrew Paniakin <apanyaki@amazon.com>
Subject: Re: Roadmap for extending DAMON beyond pte-accessed bit
Date: Sun,  6 Sep 2026 15:43:21 +0800	[thread overview]
Message-ID: <20260906074341.29976-1-lianux.mm@gmail.com> (raw)
In-Reply-To: <20260905171537.84217-1-sj@kernel.org>

On Sat,  5 Sep 2026 10:15:36 -0700 SJ Park <sj@kernel.org> wrote:

> Therefore, I believe we can consider milestone 1 nearly done.
> [...] 
> So I believe it is the time to start milestone 2.

Hi SJ,

Thanks for the roadmap update.  This direction makes sense to me.

I plan to align the Arm SPE extension with the common
damon_report_access()/data-attribute infrastructure and coordinate it with
the AMD IBS work, rather than developing a separate interface.  I will follow
the upcoming patches and would be happy to help review and test the common
infrastructure and the IBS series.  I will also track the remaining work
needed to bring the SPE support upstream.

I would also be happy to take on some related implementation work.  For my
earlier DAMOS_SPLIT work, I am now preparing v4 with this direction in mind.
We are designing representative workloads, collecting data, and exploring a
few design options before deciding the exact shape of the next revision.

Thanks,
Lian

  reply	other threads:[~2026-09-06  7:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 22:52 Roadmap for extending DAMON beyond pte-accessed bit SeongJae Park
2026-05-26  0:12 ` Ravi Jonnalagadda
2026-05-26 14:29 ` Akinobu Mita
2026-05-26 21:46   ` Ravi Jonnalagadda
2026-05-27  0:11     ` SeongJae Park
2026-06-24 14:56 ` SeongJae Park
2026-07-11  0:48   ` SJ Park
2026-09-05 16:52     ` SJ Park
2026-09-05 17:15 ` SJ Park
2026-09-06  7:43   ` Lian Wang [this message]
2026-09-06 16:36     ` SJ 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=20260906074341.29976-1-lianux.mm@gmail.com \
    --to=lianux.mm@gmail.com \
    --cc=akinobu.mita@gmail.com \
    --cc=apanyaki@amazon.com \
    --cc=damon@lists.linux.dev \
    --cc=ravis.opensrc@gmail.com \
    --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