From: Dev Jain <dev.jain@arm.com>
To: Wen Jiang <jiangwenxiaomi@gmail.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, david@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, rppt@kernel.org,
ryan.roberts@arm.com, "Barry Song (Xiaomi)" <baohua@kernel.org>,
Wen Jiang <jiangwen6@xiaomi.com>, Leo Yan <leo.yan@arm.com>
Subject: Re: [PATCH v6 5/6] mm/vmalloc: map contiguous pages in batches for vmap() if possible
Date: Tue, 14 Jul 2026 11:03:34 +0530 [thread overview]
Message-ID: <a9fe7408-8607-4115-8f2f-75ec9b5a4b21@arm.com> (raw)
In-Reply-To: <CAHKocdG7iO=S+pZLSs+mYO3GmVC_WvpC0V_1Tjj7RZ-YxWVh_w@mail.gmail.com>
On 14/07/26 10:46 am, Wen Jiang wrote:
> On Mon, 13 Jul 2026 at 23:19, Dev Jain <dev.jain@arm.com> wrote:
>>
>>
>>
>> On 09/07/26 1:08 pm, Wen Jiang wrote:
>>> From: "Barry Song (Xiaomi)" <baohua@kernel.org>
>>>
>>> In many cases, the pages passed to vmap() may include high-order
>>> pages. For example, the systemheap often allocates pages in descending
>>> order: order 8, then 4, then 0. Currently, vmap() iterates over every
>>> page individually—even pages inside a high-order block are handled
>>> one by one.
>>>
>>> This patch detects physically contiguous pages (regardless of whether
>>> they are compound or non-compound) by scanning with
>>> num_pages_contiguous(), and maps them as a single contiguous block
>>> whenever possible. The mapping order is determined by taking the
>>> minimum of the contiguous page count and the pfn alignment, allowing
>>> graceful degradation when pfn alignment is less than the contiguous
>>> range.
>>>
>>> Pages with the same page_shift are coalesced and mapped via
>>> vmap_pages_range_noflush_walk() to avoid page table rewalk.
>>>
>>> As users typically allocate memory in descending orders (e.g.
>>> 8 → 4 → 0), once an order-0 page is encountered, we stop scanning
>>> for contiguous pages since subsequent pages are likely order-0 as well.
>>>
>>> Signed-off-by: Barry Song (Xiaomi) <baohua@kernel.org>
>>> Co-developed-by: Dev Jain <dev.jain@arm.com>
>>> Signed-off-by: Dev Jain <dev.jain@arm.com>
>>> Signed-off-by: Wen Jiang <jiangwen6@xiaomi.com>
>>> Tested-by: Xueyuan Chen <xueyuan.chen21@gmail.com>
>>> Tested-by: Leo Yan <leo.yan@arm.com>
>>> ---
>>> mm/vmalloc.c | 87 ++++++++++++++++++++++++++++++++++++++++++++++++++--
>>> 1 file changed, 85 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
>>> index d2a4d649af549..db0492151ad08 100644
>>> --- a/mm/vmalloc.c
>>> +++ b/mm/vmalloc.c
>>> @@ -3543,6 +3543,89 @@ void vunmap(const void *addr)
>>> }
>>> EXPORT_SYMBOL(vunmap);
>>>
>>> +static inline unsigned int vm_shift(pgprot_t prot, unsigned long size)
>>> +{
>>> + if (arch_vmap_pmd_supported(prot) && size >= PMD_SIZE)
>>> + return PMD_SHIFT;
>>> +
>>> + return arch_vmap_pte_supported_shift(size);
>>> +}
>>
>> Need to throw in a preparatory patch for this, which will (in addition to
>> introduction of the vm_shift() function) do:
>>
>
> Hi Dev,
>
> Your suggestion is to extract "vm_shift" into a separate patch, say
> Patch 5, to make it a common utility function just like Patch 3. And
> move the existing code that can use vm_shift into this new patch as
> well, correct?
Yes it will look like the current patch 3. So before the current patch 5,
you can have a patch introducing vm_shift and making the code chunk
in __vmalloc_node_range_noprof() call it.
>
> Thanks,
> Wen
>
>> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
>> index afaa14ebf17bb..dac87e1cd484b 100644
>> --- a/mm/vmalloc.c
>> +++ b/mm/vmalloc.c
>> @@ -4175,10 +4175,7 @@ void *__vmalloc_node_range_noprof(unsigned long size, unsigned long align,
>> * supporting them.
>> */
>>
>> - if (arch_vmap_pmd_supported(prot) && size >= PMD_SIZE)
>> - shift = PMD_SHIFT;
>> - else
>> - shift = arch_vmap_pte_supported_shift(size);
>> + shift = vm_shift(prot, size);
>>
>> align = max(original_align, 1UL << shift);
>> }
>>
>>
>>
>>> +
>>> +static inline int get_vmap_batch_order(struct page **pages,
>>> + pgprot_t prot, unsigned int max_steps, unsigned int idx)
>>> +{
>>> + unsigned int nr_contig;
>>> + int order;
>>> +
>>> + if (!IS_ENABLED(CONFIG_HAVE_ARCH_HUGE_VMAP))
>>> + return 0;
>>> +
>>> + nr_contig = num_pages_contiguous(&pages[idx], max_steps);
>>> + if (nr_contig < 2)
>>> + return 0;
>>> +
>>> + order = ilog2(nr_contig);
>>> +
>>> + /* Limit order by pfn alignment */
>>> + order = min_t(int, order, __ffs(page_to_pfn(pages[idx])));
>>
>> You missed Sashiko's point here :) the pfn may be zero and this
>> will blow up. You can just first derive the pfn and do the clamping
>> only when pfn > 0.
>>
>>
>
> Will fix this.
>
> Thanks,
> Wen
>>
>>> +
>>> + if (vm_shift(prot, PAGE_SIZE << order) == PAGE_SHIFT)
>>> + return 0;
>>> +
>>> + return order;
>>> +}
>>> +
next prev parent reply other threads:[~2026-07-14 5:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 7:38 [PATCH v6 0/6] mm/vmalloc: Speed up ioremap, vmalloc and vmap with contiguous memory Wen Jiang
2026-07-09 7:38 ` [PATCH v6 1/6] arm64/hugetlb: Extend batching of multiple CONT_PTE in a single PTE setup Wen Jiang
2026-07-14 6:54 ` Anshuman Khandual
2026-07-14 8:35 ` Wen Jiang
2026-07-09 7:38 ` [PATCH v6 2/6] arm64/vmalloc: Allow arch_vmap_pte_range_map_size to batch multiple CONT_PTE Wen Jiang
2026-07-14 7:13 ` Anshuman Khandual
2026-07-14 9:24 ` Wen Jiang
2026-07-15 2:49 ` Wen Jiang
2026-07-15 3:31 ` Anshuman Khandual
2026-07-09 7:38 ` [PATCH v6 3/6] mm/vmalloc: Extract vmap_set_ptes() to consolidate PTE mapping logic Wen Jiang
2026-07-09 7:38 ` [PATCH v6 4/6] mm/vmalloc: Extend page table walk to support larger page_shift sizes and eliminate page table rewalk Wen Jiang
2026-07-13 13:49 ` Dev Jain
2026-07-14 6:10 ` Wen Jiang
2026-07-14 6:45 ` Dev Jain
2026-07-13 14:33 ` Dev Jain
2026-07-09 7:38 ` [PATCH v6 5/6] mm/vmalloc: map contiguous pages in batches for vmap() if possible Wen Jiang
2026-07-13 15:19 ` Dev Jain
2026-07-14 5:16 ` Wen Jiang
2026-07-14 5:33 ` Dev Jain [this message]
2026-07-14 4:59 ` Dev Jain
2026-07-09 7:38 ` [PATCH v6 6/6] mm/vmalloc: align vm_area so vmap() can batch mappings Wen Jiang
2026-07-14 5:05 ` Dev Jain
2026-07-09 23:08 ` [PATCH v6 0/6] mm/vmalloc: Speed up ioremap, vmalloc and vmap with contiguous memory Andrew Morton
2026-07-10 8:54 ` Wen Jiang
2026-07-10 8:59 ` Wen Jiang
2026-07-13 15:13 ` Dev Jain
2026-07-13 17:30 ` Uladzislau Rezki
2026-07-14 4:34 ` Dev Jain
2026-07-14 8:36 ` Anshuman Khandual
2026-07-14 11:17 ` Dev Jain
2026-07-15 3:31 ` Wen Jiang
2026-07-15 4:05 ` Anshuman Khandual
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=a9fe7408-8607-4115-8f2f-75ec9b5a4b21@arm.com \
--to=dev.jain@arm.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=david@kernel.org \
--cc=jiangwen6@xiaomi.com \
--cc=jiangwenxiaomi@gmail.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=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=urezki@gmail.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
all inboxes | Powered by JetHome®