From: "Li Zhe" <lizhe.67@bytedance.com>
To: "Balbir Singh" <balbirs@nvidia.com>
Cc: <muchun.song@linux.dev>, <osalvador@suse.de>, <david@kernel.org>,
<akpm@linux-foundation.org>, <rppt@kernel.org>,
<apopple@nvidia.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] mm/hugetlb: optimize bootmem hugepage tail vmemmap init
Date: Mon, 9 Nov 2026 17:22:24 +0800 [thread overview]
Message-ID: <3e5a9f27-ea35-4557-95d1-70ce359e4c92@bytedance.com> (raw)
In-Reply-To: <ca38db3a-a8fe-47c3-8813-5c3b0ac4b7ac@bytedance.com>
On 11/9/26 11:01 AM, Li Zhe wrote:
>
> On 11/6/26 6:23 PM, Balbir Singh wrote:
>> On Thu, Nov 05, 2026 at 08:06:15PM +0800, Li Zhe wrote:
>>> Boot-time HugeTLB allocation has to initialize tail struct pages itself
>>> when HugeTLB vmemmap optimization (HVO) is unavailable or fails. For
>>> gigantic pages, this can cover a large number of tail pages. Most state
>>> installed by __init_single_page() and prep_compound_tail() is identical
>>> for every tail page in the same huge page; only PFN-dependent fields
>>> need refreshing.
>>>
>>> Initialize the first tail page normally, copy it into a local template,
>>> then initialize the remaining tails from that template with
>>> memmap_init_page_from_template(). This avoids repeatedly doing the
>>> full
>>> __init_single_page() and prep_compound_tail() sequence for state
>>> that is
>>> identical across tail pages in the same huge page.
>>>
>>> On an arm64 QEMU/KVM guest using 4K pages and 64 boot-time 1G hugepages
>>> (HVO unavailable on arm64 in v7.4-rc1), the measured fallback tail
>>> initialization time improved by 36.43%, measured with a temporary
>>> jiffies-based printk modeled after the existing timing in
>>> memmap_init_zone_device():
>>>
>>> base: 318.4 ms
>>> with this patch: 202.4 ms
>>>
>>> Signed-off-by: Li Zhe <lizhe.67@bytedance.com>
>>> ---
>>> mm/hugetlb.c | 23 ++++++++++++++++++-----
>>> 1 file changed, 18 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
>>> index da5d04edf7c1..987f16a5ea27 100644
>>> --- a/mm/hugetlb.c
>>> +++ b/mm/hugetlb.c
>>> @@ -3219,19 +3219,32 @@ static void __init
>>> hugetlb_folio_init_tail_vmemmap(struct folio *folio,
>>> enum zone_type zone = folio_zonenum(folio);
>>> int nid = folio_nid(folio);
>>> struct page *page = folio_page(folio, start_page_number);
>>> + struct page template;
>>> unsigned long head_pfn = folio_pfn(folio);
>>> unsigned long pfn, end_pfn = head_pfn + end_page_number;
>>> unsigned int order = huge_page_order(h);
>>> + if (start_page_number >= end_page_number)
>>> + return;
>>> +
>> Can this actually happen?
>
>
> No, current callers always pass a non-empty range. I kept this to
> preserve the old for-loop no-op semantics for an empty range, but it is
> not needed here. I will remove it in v2.
I need to correct this. A local Sashiko run pointed out that the bootmem
fallback caller can pass an empty range on SuperH.
SuperH supports a 64M HugeTLB page size, and with 64K base pages
pages_per_huge_page(h) is 1024. HUGETLB_VMEMMAP_RESERVE_PAGES is
PAGE_SIZE / sizeof(struct page), which can also be 1024 or larger on a
32-bit SuperH configuration.
In that case the old for loop is a no-op. So I will keep the empty-range
check in v2, before creating the seed template.
Thanks,
Zhe
>
>>
>>> /*
>>> * As we marked all tail pages with
>>> memblock_reserved_mark_noinit(),
>>> * we must initialize them ourselves here.
>>> */
>>> - for (pfn = head_pfn + start_page_number; pfn < end_pfn; page++,
>>> pfn++) {
>>> - __init_single_page(page, pfn, zone, nid);
>>> - prep_compound_tail(page, &folio->page, order);
>>> - set_page_count(page, 0);
>>> - }
>>> + pfn = head_pfn + start_page_number;
>>> +
>>> + /*
>>> + * Seed a template from the first real tail page and refresh only
>>> + * PFN-dependent fields before copying it.
>>> + */
>>> + __init_single_page(page, pfn, zone, nid);
>>> + prep_compound_tail(page, &folio->page, order);
>>> + set_page_count(page, 0);
>>> + memcpy(&template, page, sizeof(template));
>> Do we need a separate template and page?
> Yes. page is the first tail page that has already been initialized
> normally. A separate template is needed so that later iterations can
> refresh the PFN-dependent fields before memcpy_nontemporal() copies the
> final state to each destination page.
>
> Thanks for the review and the Ack.
>
> Thanks,
> Zhe
>
>>
>>> +
>>> + for (pfn++; pfn < end_pfn; pfn++)
>>> + memmap_init_page_from_template(pfn_to_page(pfn), pfn, zone,
>>> + &template);
>>> }
>>> static void __init hugetlb_folio_init_vmemmap(struct folio *folio,
>> Acked-by: Balbir Singh <balbirs@nvidia.com>
next prev parent reply other threads:[~2026-11-09 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 12:06 [PATCH 0/2] mm: optimize HugeTLB bootmem hugepage init Li Zhe
2026-11-05 12:06 ` [PATCH 1/2] mm/mm_init: factor out memmap_init_page_from_template() Li Zhe
2026-11-06 10:34 ` Balbir Singh
2026-11-09 2:51 ` Li Zhe
2026-11-09 2:57 ` Muchun Song
2026-11-09 3:05 ` Li Zhe
2026-11-05 12:06 ` [PATCH 2/2] mm/hugetlb: optimize bootmem hugepage tail vmemmap init Li Zhe
2026-11-06 10:23 ` Balbir Singh
2026-11-09 3:01 ` Li Zhe
2026-11-09 9:22 ` Li Zhe [this message]
2026-11-09 9:41 ` Mike Rapoport
2026-11-09 9:52 ` Li Zhe
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=3e5a9f27-ea35-4557-95d1-70ce359e4c92@bytedance.com \
--to=lizhe.67@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=rppt@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®