[lkml]   [2021]   [Oct]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] hugetlb: Support node specified when using cma for gigantic hugepages

On 2021/10/11 4:55, Andrew Morton wrote:
> On Sun, 10 Oct 2021 13:24:08 +0800 Baolin Wang <> wrote:
>> Now the size of CMA area for gigantic hugepages runtime allocation is
>> balanced for all online nodes, but we also want to specify the size of
>> CMA per-node, or only one node in some cases, which are similar with
> Please describe in full detail why "we want to" do this. In other
> words, what is the benefit to our users? What are the use-cases, etc?

Sure. On some multi-nodes systems, each node's memory can be different,
allocating the same size of CMA for each node is not suitable for the
low-memory nodes. Meanwhile some workloads like DPDK mentioned by
Zhenguo only need hugepages in one node.

On the other hand, we have some machines with multiple types of memory,
like DRAM and PMEM (persistent memory). On this system, we may want to
specify all the hugepages on DRAM node, or specify the proportion of
DRAM node and PMEM node, to tuning the performance of the workloads.

 \ /
  Last update: 2021-10-11 04:14    [W:0.118 / U:1.340 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site