linux-kernel - Re: [PATCH] dma-contiguous: support numa CMA for specified node

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20230710132611.ccf619f06f3ead06986cb7f4@linux-foundation.org>
Date:   Mon, 10 Jul 2023 13:26:11 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Yajun Deng <yajun.deng@...ux.dev>
Cc:     corbet@....net, hch@....de, m.szyprowski@...sung.com,
        robin.murphy@....com, paulmck@...nel.org, catalin.marinas@....com,
        rdunlap@...radead.org, peterz@...radead.org, rostedt@...dmis.org,
        kim.phillips@....com, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, iommu@...ts.linux.dev,
        linux-mm@...ck.org
Subject: Re: [PATCH] dma-contiguous: support numa CMA for specified node

On Mon, 10 Jul 2023 15:49:44 +0800 Yajun Deng <yajun.deng@...ux.dev> wrote:

> The kernel parameter 'cma_pernuma=' only supports reserving the same
> size of CMA area for each node. We need to reserve different sizes of
> CMA area for specified nodes if these devices belong to different nodes.
> 
> Change kernel parameter from 'cma_pernuma=' to 'numa_cma='. If node
> isn't specified, it will reserve CMA area for per-numa node. if the node
> is specified, it will reserve CMA area for the specified node.
> 
> At the same time, print the node id in cma_declare_contiguous_nid() if
> enabled CONFIG_NUMA.

Changing an existing kernel parameter will break existing setups.  It
would be preferable to add a new parameter for this?