From: lirongqing <lirongqing@baidu.com>
To: <muchun.song@linux.dev>, <osalvador@suse.de>, <david@redhat.com>,
<akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Cc: Li RongQing <lirongqing@baidu.com>
Subject: [PATCH] mm/hugetlb: skip report_hugepages() output when no hugepages configured
Date: Wed, 10 Sep 2025 17:03:16 +0800 [thread overview]
Message-ID: <20250910090316.3406-1-lirongqing@baidu.com> (raw)
From: Li RongQing <lirongqing@baidu.com>
Avoid unnecessary report_hugepages() output and processing when
max_huge_pages is 0. This eliminates redundant log messages for
unconfigured hugepage sizes and saves CPU cycles during boot.
Before this change, the kernel would always print registration messages
even for hugepage sizes with zero pre-allocated pages:
[ 4.118953] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 4.122920] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page
[ 4.126920] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[ 4.130920] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page
Now these messages are suppressed when no pages are configured.
Signed-off-by: Li RongQing <lirongqing@baidu.com>
---
mm/hugetlb.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index af7c36f..9fb9311 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -3733,6 +3733,9 @@ static void __init report_hugepages(void)
for_each_hstate(h) {
char buf[32];
+ if (!h->max_huge_pages)
+ continue;
+
nrinvalid = hstate_boot_nrinvalid[hstate_index(h)];
h->max_huge_pages -= nrinvalid;
--
2.9.4
next reply other threads:[~2025-09-10 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 9:03 lirongqing [this message]
2025-09-10 9:09 ` David Hildenbrand
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=20250910090316.3406-1-lirongqing@baidu.com \
--to=lirongqing@baidu.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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