From: sashiko-bot@kernel.org
To: "Gregory Price (Meta)" <gourry@gourry.net>
Cc: damon@lists.linux.dev
Subject: Re: [PATCH] mm/damon: use damon_get_monitor_folio() for hugetlb entries
Date: Fri, 02 Oct 2026 14:14:21 +0000 [thread overview]
Message-ID: <20261002141421.AF3431F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261002140727.701709-1-gourry@gourry.net>
> From: Gregory Price <gourry@gourry.net>
>
> Hugetlb folio acquisition is open-coded in three places:
> - damon_hugetlb_mkold()
> - damon_young_hugetlb_entry()
> - damon_va_probe_hugetlb_entry()
>
> DAMON already has damon_get_monitor_folio(), which paddr uses to
> get monitored LRU and hugetlb folios and to filter them through
> damon_folio_acceptable(). These paths bypass that check.
>
> Use that helper in these paths too, so that DAMON acquires hugetlb
> folios and applies its acceptance policy in one place.
>
> No functional change intended. All callers reach these paths with a
> present hugetlb PTE under the page table lock, so the folio is always
> a mapped hugetlb folio and the helper always returns it.
>
> Signed-off-by: Gregory Price (Meta) <gourry@gourry.net>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261002140727.701709-1-gourry@gourry.net?part=1
next prev parent reply other threads:[~2026-10-02 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 14:07 [PATCH] mm/damon: use damon_get_monitor_folio() for hugetlb entries Gregory Price (Meta)
2026-10-02 14:14 ` sashiko-bot [this message]
2026-10-02 18:11 ` SJ Park
2026-10-02 18:28 ` Gregory Price
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=20261002141421.AF3431F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=damon@lists.linux.dev \
--cc=gourry@gourry.net \
--cc=sashiko-reviews@lists.linux.dev \
/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