[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8db5f7f3b66a40af8abf921290db42ab@baidu.com>
Date: Thu, 14 Aug 2025 09:12:06 +0000
From: "Li,Rongqing" <lirongqing@...du.com>
To: David Hildenbrand <david@...hat.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 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
Br
-Li
> --
> Cheers
>
> David / dhildenb
Powered by blists - more mailing lists