From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Baolin Wang <baolin.wang@linux.alibaba.com>, 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 v2 4/6] mm: add a batched helper to clear the young flag for large folios
Date: Tue, 3 Mar 2026 09:51:00 +0100 [thread overview]
Message-ID: <c56f4fe6-165b-435d-86bb-ad6a548990b5@kernel.org> (raw)
In-Reply-To: <7b4266c8-f885-44fb-b39b-aee38625980c@linux.alibaba.com>
On 3/3/26 03:36, Baolin Wang wrote:
>
>
> On 3/2/26 5:07 PM, David Hildenbrand (Arm) wrote:
>> On 2/27/26 10:44, Baolin Wang wrote:
>>> Currently, MGLRU will call ptep_test_and_clear_young_notify() to
>>> check and
>>> clear the young flag for each PTE sequentially, which is inefficient for
>>> large folios reclamation.
>>>
>>> Moreover, on Arm64 architecture, which supports contiguous PTEs, the
>>> Arm64-
>>> specific ptep_test_and_clear_young() already implements an
>>> optimization to
>>> clear the young flags for PTEs within a contiguous range. However,
>>> this is not
>>> sufficient. Similar to the Arm64 specific clear_flush_young_ptes(),
>>> we can
>>> extend this to perform batched operations for the entire large folio
>>> (which
>>> might exceed the contiguous range: CONT_PTE_SIZE).
>>>
>>> Thus, we can introduce a new batched helper:
>>> test_and_clear_young_ptes() and
>>> its wrapper test_and_clear_young_ptes_notify() which are consistent
>>> with the
>>> existing functions, to perform batched checking of the young flags
>>> for large
>>> folios, which can help improve performance during large folio
>>> reclamation when
>>> MGLRU is enabled. And it will be overridden by the architecture that
>>> implements
>>> a more efficient batch operation in the following patches.
>>>
>>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>>> ---
>>> include/linux/pgtable.h | 38 ++++++++++++++++++++++++++++++++++++++
>>> mm/internal.h | 16 +++++++++++-----
>>> 2 files changed, 49 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/include/linux/pgtable.h b/include/linux/pgtable.h
>>> index 776993d4567b..29bd9fd04e1e 100644
>>> --- a/include/linux/pgtable.h
>>> +++ b/include/linux/pgtable.h
>>> @@ -1103,6 +1103,44 @@ static inline int
>>> clear_flush_young_ptes(struct vm_area_struct *vma,
>>> }
>>> #endif
>>> +#ifndef test_and_clear_young_ptes
>>> +/**
>>> + * test_and_clear_young_ptes - Mark PTEs that map consecutive pages
>>> of the same
>>> + * folio as old
>>> + * @vma: The virtual memory area the pages are mapped into.
>>> + * @addr: Address the first page is mapped at.
>>> + * @ptep: Page table pointer for the first entry.
>>> + * @nr: Number of entries to clear access bit.
>>> + *
>>> + * May be overridden by the architecture; otherwise, implemented as
>>> a simple
>>> + * loop over ptep_test_and_clear_young().
>>> + *
>>> + * Note that PTE bits in the PTE range besides the PFN can differ.
>>> For example,
>>> + * some PTEs might be write-protected.
>>> + *
>>> + * Context: The caller holds the page table lock. The PTEs map
>>> consecutive
>>> + * pages that belong to the same folio. The PTEs are all in the
>>> same PMD.
>>> + *
>>> + * Returns: whether any PTE was young.
>>> + */
>>> +static inline int test_and_clear_young_ptes(struct vm_area_struct *vma,
>>> + unsigned long addr, pte_t *ptep,
>>> + unsigned int nr)
>>
>> Two tabs ...
>
> Ah, yes, not sure why I missed this one :(
>
>> What happened to using a boolen as return type and for "int young"?
> As I replied to you previously [1], I’d like to do this in a follow-up
> patchset that converts all functions that check the young flag. Does
> that sound OK to you?
>
> [1] https://lore.kernel.org/all/32c538ce-6af8-48a8-86fc-
> d26ee253af54@linux.alibaba.com/
Oh, missed that. Works for me.
--
Cheers,
David
next prev parent reply other threads:[~2026-03-03 8:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 9:44 [PATCH v2 0/6] support batched checking of the young flag for MGLRU Baolin Wang
2026-02-27 9:44 ` [PATCH v2 1/6] mm: use inline helper functions instead of ugly macros Baolin Wang
2026-02-27 9:44 ` [PATCH v2 2/6] mm: rename ptep/pmdp_clear_young_notify() to ptep/pmdp_test_and_clear_young_notify() Baolin Wang
2026-03-02 9:06 ` David Hildenbrand (Arm)
2026-02-27 9:44 ` [PATCH v2 3/6] mm: rmap: add a ZONE_DEVICE folio warning in folio_referenced() Baolin Wang
2026-02-27 9:44 ` [PATCH v2 4/6] mm: add a batched helper to clear the young flag for large folios Baolin Wang
2026-03-02 9:07 ` David Hildenbrand (Arm)
2026-03-03 2:36 ` Baolin Wang
2026-03-03 8:51 ` David Hildenbrand (Arm) [this message]
2026-02-27 9:44 ` [PATCH v2 5/6] mm: support batched checking of the young flag for MGLRU Baolin Wang
2026-03-02 9:57 ` David Hildenbrand (Arm)
2026-03-03 6:03 ` Baolin Wang
2026-03-03 8:57 ` David Hildenbrand (Arm)
2026-02-27 9:44 ` [PATCH v2 6/6] arm64: mm: implement the architecture-specific test_and_clear_young_ptes() Baolin Wang
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=c56f4fe6-165b-435d-86bb-ad6a548990b5@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=catalin.marinas@arm.com \
--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