[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7b8f4380-d74d-4498-9e14-b1302f1dec0b@redhat.com>
Date: Thu, 14 Aug 2025 11:15:27 +0200
From: David Hildenbrand <david@...hat.com>
To: "Li,Rongqing" <lirongqing@...du.com>,
"muchun.song@...ux.dev" <muchun.song@...ux.dev>,
"osalvador@...e.de" <osalvador@...e.de>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [外部邮件] Re: [PATCH] mm/hugetlb: early exit from hugetlb_pages_alloc_boot() when max_huge_pages=0
On 14.08.25 11:12, Li,Rongqing wrote:
>> On 14.08.25 10:29, lirongqing wrote:
>>> From: Li RongQing <lirongqing@...du.com>
>>>
>>> Optimize hugetlb_pages_alloc_boot() to return immediately when
>>> max_huge_pages is 0, saving cycles when hugepages aren't configured in
>>> the kernel command line.
>>
>> Do we really care?
>>
>
> I find this when I see the boot log, I think this log is unnecessary if user did not configure hugetlbfs in kernel cmdline
>
> kernel: HugeTLB: allocation took 0ms with hugepage_allocation_threads=32
That's valuable information to add to the patch description :)
--
Cheers
David / dhildenb
Powered by blists - more mailing lists