linux-kernel - Re: [PATCH v8] hugetlbfs: Extend the definition of hugepages parameter to support node allocation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 5 Oct 2021 15:59:48 -0700
From:   Mike Kravetz <mike.kravetz@...cle.com>
To:     Zhenguo Yao <yaozhenguo1@...il.com>, akpm@...ux-foundation.org
Cc:     dan.carpenter@...cle.com, nathan@...nel.org, mpe@...erman.id.au,
        benh@...nel.crashing.org, paulus@...ba.org, corbet@....net,
        rppt@...nel.org, yaozhenguo@...com, willy@...radead.org,
        linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-mm@...ck.org
Subject: Re: [PATCH v8] hugetlbfs: Extend the definition of hugepages
 parameter to support node allocation

On 10/4/21 10:47 PM, Zhenguo Yao wrote:
> We can specify the number of hugepages to allocate at boot. But the
> hugepages is balanced in all nodes at present. In some scenarios,
> we only need hugepages in one node. For example: DPDK needs hugepages
> which are in the same node as NIC.
> 
> If DPDK needs four hugepages of 1G size in node1 and system has 16 numa
> nodes we must reserve 64 hugepages on the kernel cmdline.  But only four
> hugepages are used.  The others should be free after boot.  If the system
> memory is low(for example: 64G), it will be an impossible task.
> 
> So extend the hugepages parameter to support specifying hugepages on a
> specific node.  For example add following parameter:
> 
> hugepagesz=1G hugepages=0:1,1:3
> 
> It will allocate 1 hugepage in node0 and 3 hugepages in node1.
> 
> Signed-off-by: Zhenguo Yao <yaozhenguo1@...il.com>
> Reviewed-by: Mike Kravetz <mike.kravetz@...cle.com>

Looks good.  Thank you!
-- 
Mike Kravetz