From: SJ Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SJ Park <sj@kernel.org>, "Liam R. Howlett" <liam@infradead.org>,
David Hildenbrand <david@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Shuah Khan <skhan@linuxfoundation.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-mm@kvack.org
Subject: Re: [PATCH 0/8] mm/damon: introduce hugepage_size probe filter
Date: Tue, 15 Sep 2026 16:49:38 -0700 [thread overview]
Message-ID: <20260915234938.98475-1-sj@kernel.org> (raw)
In-Reply-To: <20260915163928.9d6260f445d895429d115fd8@linux-foundation.org>
On Tue, 15 Sep 2026 16:39:28 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Tue, 15 Sep 2026 07:33:49 -0700 SJ Park <sj@kernel.org> wrote:
>
> > Knowing whether a given memory is backed by a hugepage of specific size
> > is useful for efficient utilization of hugepages. For easy monitoring
> > of the information, introduce a new data attribute probe filter type,
> > hugepage_size. It works similar to the DAMOS filter of the same name.
> > It works for memory that is backed by a hugepage of a given size range.
> >
> > Patch 1 introduces the new probe filter type to DAMON API and extends
> > related data structures. Patch 2 updates probe filter commit logic to
> > handle the size range. Patch 3 Updates the filtering logic to support
> > the new type. Patch 4 adds new DAMON sysfs files for the size range.
> > Patch 5 updates DAMON sysfs interface to fully support the new filter
> > type. Patches 6-8 updates design, usage and ABI documents for the new
> > feature.
>
> All queued up, thanks. With a -fix for [7/8].
>
> > Test
>
> fyi, I'm always reluctant to include testing info in the permanent
> record. Because it's development-time info which becomes obsolete very
> quickly.
>
> It isn't useful to someone who is reading the changelog in mainline in
> 2028 (or even Nov 2026) because the patchset will have had far more testing
> since these words were written.
>
> It is of course very useful info but I suggest it be maintained below
> the "---", where all short-term development-time info is best
> maintained.
Agreed. I will do so for individual patches. For cover letters that don't
have the "---" lines, I will add an informal note saying "please do not add
below to the commit message". If you prefer, I could add "---" line on the
cover letter instead of the informal note. Or, I could add the informal note
below the manual "---" line, too. Let me know if you prefer that.
Thanks,
SJ
next prev parent reply other threads:[~2026-09-15 23:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 14:33 SJ Park
2026-09-15 14:33 ` [PATCH 1/8] mm/damon/api: introduce DAMON_FILTER_TYPE_HUGEPAGE_SIZE SJ Park
2026-09-15 14:33 ` [PATCH 2/8] mm/damon/core: commit hugepage_size type damon filter SJ Park
2026-09-15 14:33 ` [PATCH 3/8] mm/damon/ops-common: support hugepage_size damon filter matching SJ Park
2026-09-15 14:33 ` [PATCH 4/8] mm/damon/sysfs: add min,max files under probe filter directory SJ Park
2026-09-15 14:33 ` [PATCH 5/8] mm/damon/sysfs: support hugepage_size probe filter SJ Park
2026-09-15 14:33 ` [PATCH 6/8] Docs/mm/damon/design: update for " SJ Park
2026-09-15 14:33 ` [PATCH 7/8] Docs/admin-guide/mm/damon/usage: update for hugepage_size SJ Park
2026-09-15 15:01 ` SJ Park
2026-09-15 14:33 ` [PATCH 8/8] Docs/ABI/damon: update for hugepage_size probe filter SJ Park
2026-09-15 14:58 ` [PATCH 0/8] mm/damon: introduce " SJ Park
2026-09-15 23:39 ` Andrew Morton
2026-09-15 23:49 ` SJ Park [this message]
2026-09-16 5:57 ` 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=20260915234938.98475-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-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rdunlap@infradead.org \
--cc=rppt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®