From: David Hildenbrand <david@redhat.com>
To: lirongqing <lirongqing@baidu.com>,
muchun.song@linux.dev, osalvador@suse.de,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/hugetlb: skip report_hugepages() output when no hugepages configured
Date: Wed, 10 Sep 2025 11:09:10 +0200 [thread overview]
Message-ID: <b5169886-1216-4d49-85f1-437ad7063fd3@redhat.com> (raw)
In-Reply-To: <20250910090316.3406-1-lirongqing@baidu.com>
On 10.09.25 11:03, lirongqing wrote:
> 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.
Well, there is valuable information in there, especially given that we
can allocate these hugetlb pages later.
So I think we want to keep printing that information.
--
Cheers
David / dhildenb
prev parent reply other threads:[~2025-09-10 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 9:03 lirongqing
2025-09-10 9:09 ` David Hildenbrand [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=b5169886-1216-4d49-85f1-437ad7063fd3@redhat.com \
--to=david@redhat.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