From: Oscar Salvador <osalvador@suse.de>
To: Li Zhe <lizhe.67@bytedance.com>
Cc: muchun.song@linux.dev, david@kernel.org,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hugetlb: increase hugepage reservations when using node-specific "hugepages=" cmdline
Date: Tue, 27 Jan 2026 14:35:54 +0100 [thread overview]
Message-ID: <aXi_OhpzvSkoJK4R@localhost.localdomain> (raw)
In-Reply-To: <20260122035002.79958-1-lizhe.67@bytedance.com>
On Thu, Jan 22, 2026 at 11:50:02AM +0800, Li Zhe wrote:
> Commit 3dfd02c90037 ("hugetlb: increase number of reserving hugepages
> via cmdline") raised the number of hugepages that can be reserved
> through the boot-time "hugepages=" parameter for the non-node-specific
> case, but left the node-specific form of the same parameter unchanged.
>
> This patch extends the same optimization to node-specific reservations.
> When HugeTLB vmemmap optimization (HVO) is enabled and a node cannot
> satisfy the requested hugepages, the code first releases ordinary
> struct-page memory of hugepages obtained from the buddy allocator,
> allowing their struct-page memory to be reclaimed and reused for
> additional hugepage reservations on that node.
>
> This is particularly beneficial for configurations that require
> identical, large per-node hugepage reservations. On a four-node, 384 GB
> x86 VM, the patch raises the attainable 2 MiB hugepage reservation from
> under 374 GB to more than 379 GB.
>
> Signed-off-by: Li Zhe <lizhe.67@bytedance.com>
Acked-by: Oscar Salvador <osalvador@suse.de>
--
Oscar Salvador
SUSE Labs
prev parent reply other threads:[~2026-01-27 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 3:50 Li Zhe
2026-01-22 3:53 ` Muchun Song
2026-01-22 22:19 ` Andrew Morton
2026-01-23 3:14 ` Li Zhe
2026-01-23 3:18 ` Andrew Morton
2026-01-27 13:35 ` Oscar Salvador [this message]
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=aXi_OhpzvSkoJK4R@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizhe.67@bytedance.com \
--cc=muchun.song@linux.dev \
/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