From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>, akpm@linux-foundation.org
Cc: catalin.marinas@arm.com, will@kernel.org,
lorenzo.stoakes@oracle.com, ryan.roberts@arm.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, riel@surriel.com,
harry.yoo@oracle.com, jannh@google.com, willy@infradead.org,
baohua@kernel.org, dev.jain@arm.com, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, hannes@cmpxchg.org,
zhengqi.arch@bytedance.com, shakeel.butt@linux.dev,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] mm: support batched checking of the young flag for MGLRU
Date: Thu, 26 Feb 2026 13:56:28 +0800 [thread overview]
Message-ID: <0871edb9-08a2-46a0-ade6-af842a12e0d3@linux.alibaba.com> (raw)
In-Reply-To: <2e7a1e24-3616-4b79-b943-b5f7efde2d31@kernel.org>
On 2/25/26 10:25 PM, David Hildenbrand (Arm) wrote:
> On 2/24/26 02:56, Baolin Wang wrote:
>> Use the batched helper clear_young_ptes_notify() to check and clear the
>> young flag to improve the performance during large folio reclamation when
>> MGLRU is enabled.
>>
>> Meanwhile, we can also support batched checking the young and dirty flag
>> when MGLRU walks the mm's pagetable to update the folios' generation
>> counter. Since MGLRU also checks the PTE dirty bit, use folio_pte_batch_flags()
>> with FPB_MERGE_YOUNG_DIRTY set to detect batches of PTEs for a large folio.
>>
>> Then we can remove the ptep_clear_young_notify() since it has no users now.
>>
>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>> ---
>
> [...]
>
>>
>> -static inline int ptep_clear_young_notify(struct vm_area_struct *vma,
>> - unsigned long addr, pte_t *ptep)
>> -{
>> - return clear_young_ptes_notify(vma, addr, ptep, 1);
>> -}
>> -
>> static inline int pmdp_clear_young_notify(struct vm_area_struct *vma,
>> unsigned long addr, pmd_t *pmdp)
>> {
>> @@ -1847,12 +1841,6 @@ static inline int pmdp_clear_young_notify(struct vm_area_struct *vma,
>> #define clear_young_ptes_notify test_and_clear_young_ptes
>> #define pmdp_clear_young_notify pmdp_test_and_clear_young
>>
>> -static inline int ptep_clear_young_notify(struct vm_area_struct *vma,
>> - unsigned long addr, pte_t *ptep)
>> -{
>> - return test_and_clear_young_ptes(vma, addr, ptep, 1);
>> -}
>> -
>
> Oh, we remove the last user, nice.
>
>
>> #endif /* CONFIG_MMU_NOTIFIER */
>>
>> #endif /* __MM_INTERNAL_H */
>> diff --git a/mm/rmap.c b/mm/rmap.c
>> index be785dfc9336..1c147251ae28 100644
>> --- a/mm/rmap.c
>> +++ b/mm/rmap.c
>> @@ -958,25 +958,21 @@ static bool folio_referenced_one(struct folio *folio,
>> return false;
>> }
>>
>> + if (pvmw.pte && folio_test_large(folio)) {
>> + unsigned long end_addr = pmd_addr_end(address, vma->vm_end);
>> + unsigned int max_nr = (end_addr - address) >> PAGE_SHIFT;
>
> Both could be const.
Ack.
>
>> + pte_t pteval = ptep_get(pvmw.pte);
>
> I wonder if there could be a way to avoid this ptep_get() by letting
> page_vma_mapped_walk() just provide the last value it used (in
> check_pte() I guess). Something for another patch.
Well, we’d need to add a new field to ‘struct page_vma_mapped_walk’ to
store the last value (e.g., pvmw.pteval), but this makes me wonder if it
is worth adding a new field just to avoid a lightweight read (which
should have no obvious performance impact).
>> +
>> + nr = folio_pte_batch(folio, pvmw.pte, pteval, max_nr);
>> + ptes += nr;
>> + }
>> +
>> if (lru_gen_enabled() && pvmw.pte) {
>> - if (lru_gen_look_around(&pvmw))
>> + if (lru_gen_look_around(&pvmw, nr))
>> referenced++;
>> } else if (pvmw.pte) {
>> - if (folio_test_large(folio)) {
>> - unsigned long end_addr = pmd_addr_end(address, vma->vm_end);
>> - unsigned int max_nr = (end_addr - address) >> PAGE_SHIFT;
>> - pte_t pteval = ptep_get(pvmw.pte);
>> -
>> - nr = folio_pte_batch(folio, pvmw.pte,
>> - pteval, max_nr);
>> - }
>> -
>> - ptes += nr;
>> if (clear_flush_young_ptes_notify(vma, address, pvmw.pte, nr))
>> referenced++;
>> - /* Skip the batched PTEs */
>> - pvmw.pte += nr - 1;
>> - pvmw.address += (nr - 1) * PAGE_SIZE;
>> } else if (IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE)) {
>> if (pmdp_clear_flush_young_notify(vma, address,
>> pvmw.pmd))
>> @@ -995,6 +991,12 @@ static bool folio_referenced_one(struct folio *folio,
>> page_vma_mapped_walk_done(&pvmw);
>> break;
>> }
>> +
>> + /* Skip the batched PTEs */
>> + if (nr > 1) {
>> + pvmw.pte += nr - 1;
>> + pvmw.address += (nr - 1) * PAGE_SIZE;
>> + }
>
> As nr >= 1, you can just unconditionaly do
>
> pvmw.pte += nr - 1;
> pvmw.address += (nr - 1) * PAGE_SIZE;
Actually, I want to filter out the THP case where the 'pvmw.pte' is
NULL. But it shouldn’t be a problem, because 'nr' is always 1 for the
THP case. I can remove the check.
>> }
>>
>> if (referenced)
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index 728868c61750..d83962468b2e 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -3494,6 +3494,7 @@ static bool walk_pte_range(pmd_t *pmd, unsigned long start, unsigned long end,
>> struct pglist_data *pgdat = lruvec_pgdat(walk->lruvec);
>> DEFINE_MAX_SEQ(walk->lruvec);
>> int gen = lru_gen_from_seq(max_seq);
>> + unsigned int nr;
>> pmd_t pmdval;
>>
>> pte = pte_offset_map_rw_nolock(args->mm, pmd, start & PMD_MASK, &pmdval, &ptl);
>> @@ -3512,11 +3513,13 @@ static bool walk_pte_range(pmd_t *pmd, unsigned long start, unsigned long end,
>>
>> lazy_mmu_mode_enable();
>> restart:
>> - for (i = pte_index(start), addr = start; addr != end; i++, addr += PAGE_SIZE) {
>> + for (i = pte_index(start), addr = start; addr != end; i += nr, addr += nr * PAGE_SIZE) {
>> unsigned long pfn;
>> struct folio *folio;
>> - pte_t ptent = ptep_get(pte + i);
>> + pte_t *ptep = pte + i;
>> + pte_t ptent = ptep_get(ptep);
>
>
> Existing "pte vs ptent" vs. "ptep vs. pte" is already confusing.
> Combining them into "pte vs. ptep vs. ptent" is no good.
>
> If you need another variable, call it "cur_pte". Or rename "pte" to
> "start_pte".
OK. "cur_pte" sounds good to me.
>> + nr = 1;
>> total++;
>> walk->mm_stats[MM_LEAF_TOTAL]++;
>>
>> @@ -3528,7 +3531,14 @@ static bool walk_pte_range(pmd_t *pmd, unsigned long start, unsigned long end,
>> if (!folio)
>> continue;
>>
>> - if (!ptep_clear_young_notify(args->vma, addr, pte + i))
>> + if (folio_test_large(folio)) {
>> + unsigned int max_nr = (end - addr) >> PAGE_SHIFT;
>> +
>> + nr = folio_pte_batch_flags(folio, NULL, ptep, &ptent,
>> + max_nr, FPB_MERGE_YOUNG_DIRTY);
>> + }
>> +
>> + if (!clear_young_ptes_notify(args->vma, addr, ptep, nr))
>> continue;
>>
>> if (last != folio) {
>> @@ -4186,7 +4196,7 @@ static void lru_gen_age_node(struct pglist_data *pgdat, struct scan_control *sc)
>> * the PTE table to the Bloom filter. This forms a feedback loop between the
>> * eviction and the aging.
>> */
>> -bool lru_gen_look_around(struct page_vma_mapped_walk *pvmw)
>> +bool lru_gen_look_around(struct page_vma_mapped_walk *pvmw, unsigned int batched)
>
> What is "batched"? Did you mean "nr_ptes" ? Or just the initial value
> for "nr" ?
There is already an 'nr' variable in this function. "nr_ptes" sounds
good to me, and will use it.
>> - if (!ptep_clear_young_notify(vma, addr, pte + i))
>> + if (folio_test_large(folio)) {
>> + unsigned int max_nr = (end - addr) >> PAGE_SHIFT;
>
> Can be const.
Ack.
>
>> +
>> + nr = folio_pte_batch_flags(folio, NULL, ptep, &ptent,
>> + max_nr, FPB_MERGE_YOUNG_DIRTY);
>> + }
>
> I guess we might benefit from a FPB_MERGE_YOUNG only here. But this
> should work.
I’ve thought about it. Instead of adding another flag and some new 'if'
branches for folio_pte_batch_flags(), and given that it brings no
performance improvement for MGLRU, I still prefer the current
FPB_MERGE_YOUNG_DIRTY method. :)
Thanks for reviewing.
next prev parent reply other threads:[~2026-02-26 5:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 1:56 [PATCH 0/5] " Baolin Wang
2026-02-24 1:56 ` [PATCH 1/5] mm: use inline helper functions instead of ugly macros Baolin Wang
2026-02-24 2:36 ` Rik van Riel
2026-02-24 7:09 ` Barry Song
2026-02-25 13:56 ` David Hildenbrand (Arm)
2026-02-26 3:36 ` Baolin Wang
2026-02-24 1:56 ` [PATCH 2/5] mm: rmap: add a ZONE_DEVICE folio warning in folio_referenced() Baolin Wang
2026-02-24 2:38 ` Rik van Riel
2026-02-24 5:49 ` Baolin Wang
2026-02-25 13:57 ` David Hildenbrand (Arm)
2026-02-24 6:34 ` Alistair Popple
2026-02-24 1:56 ` [PATCH 3/5] mm: add a batched helper to clear the young flag for large folios Baolin Wang
2026-02-24 22:03 ` Rik van Riel
2026-02-25 2:05 ` Baolin Wang
2026-02-25 14:04 ` David Hildenbrand (Arm)
2026-02-26 3:42 ` Baolin Wang
2026-02-24 1:56 ` [PATCH 4/5] mm: support batched checking of the young flag for MGLRU Baolin Wang
2026-02-24 22:12 ` Rik van Riel
2026-02-25 14:25 ` David Hildenbrand (Arm)
2026-02-26 5:56 ` Baolin Wang [this message]
2026-02-24 1:56 ` [PATCH 5/5] arm64: mm: implement the architecture-specific test_and_clear_young_ptes() Baolin Wang
2026-02-25 0:23 ` Rik van Riel
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=0871edb9-08a2-46a0-ade6-af842a12e0d3@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=weixugc@google.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yuanchu@google.com \
--cc=zhengqi.arch@bytedance.com \
/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