[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<642590c8685a8ff8c042d628336bc7380217ee16.camel@cyberus-technology.de>
Date: Tue, 25 Feb 2025 13:01:47 +0000
From: Thomas Prescher <thomas.prescher@...erus-technology.de>
To: "fvdl@...gle.com" <fvdl@...gle.com>
CC: "linux-mm@...ck.org" <linux-mm@...ck.org>, "corbet@....net"
<corbet@....net>, "muchun.song@...ux.dev" <muchun.song@...ux.dev>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/2] mm: hugetlb: add hugetlb_alloc_threads cmdline option
On Mon, 2025-02-24 at 09:37 -0800, Frank van der Linden wrote:
>
> Maybe mention that this does not apply to 'gigantic' hugepages (e.g.
> hugetlb pages of an order > MAX_PAGE_ORDER). Those are allocated
> earlier in boot by memblock, in a single-threaded environment.
>
> Not your fault that this distinction between these types of hugetlb
> pages isn't clear in the Docs, of course. Only hugetlb_cma mentions
> that it is for gigantic pages. But it's probably best to mention that
> the threads parameter is for non-gigantic hugetlb pages only.
>
> - Frank
Very good point. I will update the documentation accordingly.
Powered by blists - more mailing lists