DAMON development mailing list
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Lian Wang <lianux.mm@gmail.com>
Cc: SJ Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Asier Gutierrez <gutierrez.asier@huawei-partners.com>,
	damon@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH v4 1/3] mm/damon: Introduce DAMOS_QUOTA_HUGEPAGE auto tuning
Date: Tue,  1 Sep 2026 21:23:43 -0700	[thread overview]
Message-ID: <20260902042344.83913-1-sj@kernel.org> (raw)
In-Reply-To: <20260902015616.57702-1-lianux.mm@gmail.com>

On Wed,  2 Sep 2026 09:56:01 +0800 Lian Wang <lianux.mm@gmail.com> wrote:

> Hi SJ,
> 
> > Seems using MTHP_STAT_NR_ANON that is exposed as 'nr_anon' can be used?
> 
> Thank you for the suggestion.  I will study MTHP_STAT_NR_ANON and nr_anon
> further, and document what I find.  We can continue discussing it by email,
> and I will be happy to review any follow-up or updated patches.
> 
> > I'm curious if you and general reviewers need or prefer to directly be Cc-ed.
> > I was naively thinking people can search and review DAMON patches by
> > subscribing to the mailing list or using the archives via lore.kernel.org like
> > tools.
> 
> I subscribe to many mailing lists, including linux-mm and DAMON, and I also
> follow patches through lore.  Direct Cc is not required, but I appreciate it
> for DAMON-related patches.  Because I care deeply about DAMON, directly Cc-ed
> messages are filtered into my important mailbox, so I can archive and review
> them quickly.

Thank you so much for your interest in DAMON, Lian.  But, the problem is that
my memory is so bad. :'(

I am maintaing mm patches review status dashboard for people who want to find
patches that waiting for their review.  It also provides the review status for
each sub-mm components [2] including DAMON [3].  Maybe finding patches that
waiting for your review from the dashboard is also a way for you?

If having the mail directly in your important mailbox is what you need, I
believe adding mails filtering rule for DAMON patches wouldn't be that
difficult.  If you use hkml, it could also help you monitoring [4] those.

Yet another systematic and long term solution that I could suggest is keep
reviewing and posting DAMON patches one by one, build more tracked records and
trusts, eventually adding your name as DAMON reviewer or maintainer on the
MAINTAINERS file.  All patches sent with get_maintainers.pl will automatically
Cc you.  It would take time and require patience, though, of course.

> 
> I am very happy to contribute to DAMON, and I look forward to continuing our
> discussions and reviews by email.

I really appreciate your interest and contributions to DAMON.  I hope it to be
continued long term!

[1] https://github.com/sjp38/mm_git_dashboard
[2] https://github.com/sjp38/mm_git_dashboard/tree/master/summary/subsystem
[3] https://github.com/sjp38/mm_git_dashboard/tree/master/summary/subsystem/DAMON
[4] https://github.com/sjp38/hackermail/blob/master/USAGE.md#monitoring-mails


Thanks,
SJ

[...]

  reply	other threads:[~2026-09-02  4:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 14:47 [PATCH v4 0/3] mm/damon: Introduce a huge page collapsing mechanism using auto tuning SJ Park
2026-08-31 14:47 ` [PATCH v4 1/3] mm/damon: Introduce DAMOS_QUOTA_HUGEPAGE " SJ Park
2026-08-31 18:16   ` sashiko-bot
2026-09-01  0:45     ` SJ Park
2026-09-01  6:58   ` Lian Wang
2026-09-01 14:23     ` SJ Park
2026-09-02  1:56       ` Lian Wang
2026-09-02  4:23         ` SJ Park [this message]
2026-09-02 15:03       ` Gutierrez Asier
2026-09-02 15:15         ` SJ Park
2026-08-31 14:47 ` [PATCH v4 2/3] mm/damon/sysfs: support hugepage_mem_bp quota goal metric SJ Park
2026-08-31 18:22   ` sashiko-bot
2026-09-01  0:46     ` SJ Park
2026-08-31 14:47 ` [PATCH v4 3/3] Docs/mm/damon/design: Document hugepage_mem_bp target metric SJ Park
2026-08-31 15:45   ` Randy Dunlap
2026-08-31 20:00     ` Randy Dunlap
2026-09-01  0:47       ` SJ Park
2026-09-01  5:20         ` Gutierrez Asier
2026-09-01  5:31           ` SJ Park
2026-08-31 18:35   ` sashiko-bot
2026-09-01  0:48     ` SJ Park
2026-09-01  0:49 ` [PATCH v4 0/3] mm/damon: Introduce a huge page collapsing mechanism using auto tuning 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=20260902042344.83913-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=gutierrez.asier@huawei-partners.com \
    --cc=lianux.mm@gmail.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