From: Wenjie Xu <xuwenjie04@baidu.com>
To: <muchun.song@linux.dev>, <osalvador@suse.de>,
<akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Wenjie Xu <xuwenjie04@baidu.com>,
Li RongQing <lirongqing@baidu.com>
Subject: [PATCH] hugetlb: two-phase hugepage allocation when reservation is high
Date: Fri, 16 May 2025 19:35:52 +0800 [thread overview]
Message-ID: <20250516113552.17648-1-xuwenjie04@baidu.com> (raw)
When the total reserved hugepages account for 95% or more of system RAM
(common in cloud computing on physical servers), allocating them all in one
go can starve the rest of the kernel and lead to OOM during early boot.
The previous hugetlb vmemmap batching change (91f386bf0772) can worsen
peak memory pressure under these conditions by deferring page frees,
exacerbating allocation failures. To prevent this, split the allocation
into two equal batches whenever
huge_reserved_pages >= total_base_pages * 95ULL / 100UL.
This change does not alter the number of padata worker threads per batch;
it merely introduces a second round of padata_do_multithreaded(). The added
overhead of restarting the worker threads is minimal.
Fixes: 91f386bf0772 ("hugetlb: batch freeing of vmemmap pages")
Co-developed-by: Li RongQing <lirongqing@baidu.com>
Signed-off-by: Li RongQing <lirongqing@baidu.com>
Signed-off-by: Wenjie Xu <xuwenjie04@baidu.com>
---
mm/hugetlb.c | 24 ++++++++++++++++++++----
1 file changed, 20 insertions(+), 4 deletions(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index 6ea1be71aa42..7bdcaab6f7ec 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -3616,12 +3616,21 @@ static unsigned long __init hugetlb_pages_alloc_boot(struct hstate *h)
.numa_aware = true
};
+ unsigned long huge_pages;
+ int i, hugetlb_page_alloc_iter;
+
+ unsigned long total_base_pages = totalram_pages();
+ unsigned long huge_reserved_pages = h->max_huge_pages << h->order;
+
+ hugetlb_page_alloc_iter = (huge_reserved_pages >= total_base_pages * 95ULL / 100UL)
+ ? 2 : 1;
+
+ huge_pages = h->max_huge_pages / hugetlb_page_alloc_iter;
+
unsigned long jiffies_start;
unsigned long jiffies_end;
job.thread_fn = hugetlb_pages_alloc_boot_node;
- job.start = 0;
- job.size = h->max_huge_pages;
/*
* job.max_threads is 25% of the available cpu threads by default.
@@ -3645,10 +3654,17 @@ static unsigned long __init hugetlb_pages_alloc_boot(struct hstate *h)
}
job.max_threads = hugepage_allocation_threads;
- job.min_chunk = h->max_huge_pages / hugepage_allocation_threads;
+ job.min_chunk = huge_pages / hugepage_allocation_threads;
jiffies_start = jiffies;
- padata_do_multithreaded(&job);
+ for (i = 0; i < hugetlb_page_alloc_iter; i++) {
+ job.start = huge_pages * i;
+ job.size = (i + 1 == hugetlb_page_alloc_iter)
+ ? h->max_huge_pages - huge_pages * i
+ : huge_pages;
+ padata_do_multithreaded(&job);
+ }
+
jiffies_end = jiffies;
pr_info("HugeTLB: allocation took %dms with hugepage_allocation_threads=%ld\n",
--
2.41.0
next reply other threads:[~2025-05-16 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 11:35 Wenjie Xu [this message]
2025-05-17 4:44 ` kernel test robot
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=20250516113552.17648-1-xuwenjie04@baidu.com \
--to=xuwenjie04@baidu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lirongqing@baidu.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
/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