From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Dev Jain <dev.jain@arm.com>
Cc: akpm@linux-foundation.org, david@redhat.com, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, baohua@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] khugepaged: Optimize __collapse_huge_page_copy_succeeded() for large folios by PTE batching
Date: Wed, 18 Jun 2025 18:26:25 +0100 [thread overview]
Message-ID: <f4de7754-e60a-4a87-9319-24b78a0c6895@lucifer.local> (raw)
In-Reply-To: <20250618102607.10551-1-dev.jain@arm.com>
On Wed, Jun 18, 2025 at 03:56:07PM +0530, Dev Jain wrote:
> Use PTE batching to optimize __collapse_huge_page_copy_succeeded().
>
> On arm64, suppose khugepaged is scanning a pte-mapped 2MB THP for collapse.
> Then, calling ptep_clear() for every pte will cause a TLB flush for every
> contpte block. Instead, clear_full_ptes() does a
> contpte_try_unfold_partial() which will flush the TLB only for the (if any)
> starting and ending contpte block, if they partially overlap with the range
> khugepaged is looking at.
>
> For all arches, there should be a benefit due to batching atomic operations
> on mapcounts due to folio_remove_rmap_ptes().
>
> No issues were observed with mm-selftests.
>
> Signed-off-by: Dev Jain <dev.jain@arm.com>
> ---
> mm/khugepaged.c | 31 +++++++++++++++++++++++--------
> 1 file changed, 23 insertions(+), 8 deletions(-)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index d45d08b521f6..649ccb2670f8 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -700,12 +700,14 @@ static void __collapse_huge_page_copy_succeeded(pte_t *pte,
> spinlock_t *ptl,
> struct list_head *compound_pagelist)
> {
> + unsigned long end = address + HPAGE_PMD_SIZE;
I assume we always enter here with aligned address...
> struct folio *src, *tmp;
> - pte_t *_pte;
> + pte_t *_pte = pte;
> pte_t pteval;
> + int nr_ptes;
>
> - for (_pte = pte; _pte < pte + HPAGE_PMD_NR;
> - _pte++, address += PAGE_SIZE) {
> + do {
> + nr_ptes = 1;
> pteval = ptep_get(_pte);
> if (pte_none(pteval) || is_zero_pfn(pte_pfn(pteval))) {
> add_mm_counter(vma->vm_mm, MM_ANONPAGES, 1);
> @@ -719,23 +721,36 @@ static void __collapse_huge_page_copy_succeeded(pte_t *pte,
> ksm_might_unmap_zero_page(vma->vm_mm, pteval);
> }
> } else {
Existing code but hate this level of indentation.
The code before was (barely) sort of ok-ish, but now it's realyl out of hand.
On the other hand, I look at __collapse_huge_page_isolate() and want to cry so I
guess this maybe is something that needs addressing outside of this patch.
> + const fpb_t flags = FPB_IGNORE_DIRTY | FPB_IGNORE_SOFT_DIRTY;
> + int max_nr_ptes;
> + bool is_large;
> +
> struct page *src_page = pte_page(pteval);
>
> src = page_folio(src_page);
> - if (!folio_test_large(src))
> + is_large = folio_test_large(src);
> + if (!is_large)
> release_pte_folio(src);
Hm, in this case right, release_pte_folio() does a folio_unlock().
Where does a large folio get unlocked?
I mean this must have been existing code because I don't see where this
happens previously either.
> +
> + max_nr_ptes = (end - address) >> PAGE_SHIFT;
> + if (is_large && max_nr_ptes != 1)
Is it really that harmful if max_nr_ptes == 1? Doesn't folio_pte_batch()
figure it out?
> + nr_ptes = folio_pte_batch(src, address, _pte,
> + pteval, max_nr_ptes,
> + flags, NULL, NULL, NULL);
> +
It'd be nice(r) if this was:
if (folio_test_large(src))
nr_ptes = folio_pte_batch(src, address, _pte,
pteval, max_nr_ptes,
flags, NULL, NULL, NULL);
else
release_pte_folio(src);
But even that is horrid because of the asymmetry.
> /*
> * ptl mostly unnecessary, but preempt has to
> * be disabled to update the per-cpu stats
> * inside folio_remove_rmap_pte().
> */
> spin_lock(ptl);
> - ptep_clear(vma->vm_mm, address, _pte);
> - folio_remove_rmap_pte(src, src_page, vma);
> + clear_full_ptes(vma->vm_mm, address, _pte, nr_ptes, false);
Be nice to use 'Liam's convention' of sticking `/* full = */ false)` on the
end here so we know what the false refers to.
> + folio_remove_rmap_ptes(src, src_page, nr_ptes, vma);
Kinda neat that folio_remove_map_pte() is jus ta define onto this with
nr_ptes == 1 :)
> spin_unlock(ptl);
> - free_folio_and_swap_cache(src);
> + free_swap_cache(src);
> + folio_put_refs(src, nr_ptes);
> }
> - }
> + } while (_pte += nr_ptes, address += nr_ptes * PAGE_SIZE, address != end);
>
> list_for_each_entry_safe(src, tmp, compound_pagelist, lru) {
> list_del(&src->lru);
> --
> 2.30.2
>
I can't see much wrong with this though, just 'yuck' at existing code
really :)
next prev parent reply other threads:[~2025-06-18 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 10:26 Dev Jain
2025-06-18 16:14 ` David Hildenbrand
2025-06-18 17:10 ` Lorenzo Stoakes
2025-06-18 17:23 ` David Hildenbrand
2025-06-18 17:26 ` David Hildenbrand
2025-06-19 3:54 ` Dev Jain
2025-06-18 17:26 ` Lorenzo Stoakes [this message]
2025-06-18 17:29 ` David Hildenbrand
2025-06-19 12:52 ` Lorenzo Stoakes
2025-06-19 3:22 ` Dev Jain
2025-06-19 12:53 ` Lorenzo Stoakes
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=f4de7754-e60a-4a87-9319-24b78a0c6895@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=ziy@nvidia.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