From: Uladzislau Rezki <urezki@gmail.com>
To: ryan.roberts@arm.com, dev.jain@arm.com
Cc: akpm@linux-foundation.org, catalin.marinas@arm.com,
linux-mm@kvack.org, urezki@gmail.com, will@kernel.org,
Xueyuan.chen21@gmail.com, ajd@linux.ibm.com,
anshuman.khandual@arm.com, baohua@kernel.org, chleroy@kernel.org,
david@kernel.org, dev.jain@arm.com, jiangwen6@xiaomi.com,
leo.yan@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
rppt@kernel.org, ryan.roberts@arm.com
Subject: Re: [PATCH v10 05/10] arm64/vmalloc: allow arch_vmap_pte_range_map_size() to batch multiple CONT_PTE
Date: Sun, 11 Oct 2026 11:45:16 +0200 [thread overview]
Message-ID: <astarANeoldvqBxc@milan> (raw)
In-Reply-To: <20261002090947.869220-6-jiangwen6@xiaomi.com>
On Fri, Oct 02, 2026 at 05:09:42PM +0800, Wen Jiang wrote:
> From: "Barry Song (Xiaomi)" <baohua@kernel.org>
>
> Allow arch_vmap_pte_range_map_size to batch across multiple CONT_PTE
> blocks, reducing both PTE setup and TLB flush iterations.
>
> Previously the function returned a single CONT_PTE_SIZE for an aligned
> range, so the caller mapped one CONT_PTE block per iteration. Now, for a
> CONT_PTE_SIZE-aligned range, it returns the largest CONT_PTE-aligned size
> that fits within both the remaining range and the caller's max_page_shift,
> so a single pte_set_huge() call installs several CONT_PTE blocks at once.
>
> Signed-off-by: Barry Song (Xiaomi) <baohua@kernel.org>
> Signed-off-by: Wen Jiang <jiangwen6@xiaomi.com>
> Tested-by: Xueyuan Chen <xueyuan.chen21@gmail.com>
> Tested-by: Leo Yan <leo.yan@arm.com>
> ---
> arch/arm64/include/asm/vmalloc.h | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/include/asm/vmalloc.h b/arch/arm64/include/asm/vmalloc.h
> index 4ec1acd3c1b34..c29704a19e276 100644
> --- a/arch/arm64/include/asm/vmalloc.h
> +++ b/arch/arm64/include/asm/vmalloc.h
> @@ -23,10 +23,12 @@ static inline unsigned long arch_vmap_pte_range_map_size(unsigned long addr,
> unsigned long end, u64 pfn,
> unsigned int max_page_shift)
> {
> + unsigned long size;
> +
> /*
> - * If the block is at least CONT_PTE_SIZE in size, and is naturally
> - * aligned in both virtual and physical space, then we can pte-map the
> - * block using the PTE_CONT bit for more efficient use of the TLB.
> + * If the range is at least CONT_PTE_SIZE and naturally aligned in both
> + * virtual and physical space, return the largest CONT_PTE-aligned size
> + * that fits, for more efficient use of the TLB.
> */
> if (max_page_shift < CONT_PTE_SHIFT)
> return PAGE_SIZE;
> @@ -40,7 +42,9 @@ static inline unsigned long arch_vmap_pte_range_map_size(unsigned long addr,
> if (!IS_ALIGNED(PFN_PHYS(pfn), CONT_PTE_SIZE))
> return PAGE_SIZE;
>
> - return CONT_PTE_SIZE;
> + size = min(end - addr, 1UL << max_page_shift);
> + size = round_down(size, CONT_PTE_SIZE);
> + return size;
> }
>
> #define arch_vmap_pte_range_unmap_size arch_vmap_pte_range_unmap_size
> --
> 2.34.1
>
This is arch/arm64 code. Can you, Jain or Ryan from ARM folk review this change?
Thank you!
--
Uladzislau Rezki
next prev parent reply other threads:[~2026-10-11 9:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 9:09 [PATCH v10 00/10] mm/vmalloc: Speed up ioremap, vmalloc and vmap with contiguous memory Wen Jiang
2026-10-02 9:09 ` [PATCH v10 01/10] arm64/mm: add pte_set_huge() and pte_clear_huge() Wen Jiang
2026-10-02 9:09 ` [PATCH v10 02/10] powerpc/8xx: add pte_set_huge() Wen Jiang
2026-10-02 9:09 ` [PATCH v10 03/10] mm/vmalloc: use pte_set_huge()/pte_clear_huge() for PTE-level block mappings Wen Jiang
2026-10-11 14:29 ` Uladzislau Rezki
2026-10-12 7:34 ` Wen Jiang
2026-10-02 9:09 ` [PATCH v10 04/10] arm64/hugetlb: drop the init_mm special case in clear_flush() Wen Jiang
2026-10-11 13:37 ` Uladzislau Rezki
2026-10-02 9:09 ` [PATCH v10 05/10] arm64/vmalloc: allow arch_vmap_pte_range_map_size() to batch multiple CONT_PTE Wen Jiang
2026-10-11 9:45 ` Uladzislau Rezki [this message]
2026-10-12 7:39 ` Dev Jain
2026-10-12 18:02 ` Uladzislau Rezki
2026-10-02 9:09 ` [PATCH v10 06/10] mm/vmalloc: extract vmap_set_ptes() to consolidate PTE mapping logic Wen Jiang
2026-10-02 9:09 ` [PATCH v10 07/10] mm/vmalloc: extend page table walk to support larger page_shift sizes and eliminate page table rewalk Wen Jiang
2026-10-02 9:09 ` [PATCH v10 08/10] mm/vmalloc: extract vm_shift() to consolidate mapping shift selection Wen Jiang
2026-10-02 9:09 ` [PATCH v10 09/10] mm/vmalloc: map contiguous pages in batches for vmap() if possible Wen Jiang
2026-10-02 9:09 ` [PATCH v10 10/10] mm/vmalloc: align vm_area so vmap() can batch mappings Wen Jiang
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=astarANeoldvqBxc@milan \
--to=urezki@gmail.com \
--cc=Xueyuan.chen21@gmail.com \
--cc=ajd@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=baohua@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chleroy@kernel.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=jiangwen6@xiaomi.com \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=will@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