From: Andrew Morton <akpm@linux-foundation.org>
To: Yajun Deng <yajun.deng@linux.dev>
Cc: corbet@lwn.net, hch@lst.de, m.szyprowski@samsung.com,
robin.murphy@arm.com, paulmck@kernel.org,
catalin.marinas@arm.com, rdunlap@infradead.org,
peterz@infradead.org, rostedt@goodmis.org, kim.phillips@amd.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH] dma-contiguous: support numa CMA for specified node
Date: Mon, 10 Jul 2023 13:26:11 -0700 [thread overview]
Message-ID: <20230710132611.ccf619f06f3ead06986cb7f4@linux-foundation.org> (raw)
In-Reply-To: <20230710074944.3501810-1-yajun.deng@linux.dev>
On Mon, 10 Jul 2023 15:49:44 +0800 Yajun Deng <yajun.deng@linux.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?
next prev parent reply other threads:[~2023-07-10 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 7:49 Yajun Deng
2023-07-10 20:26 ` Andrew Morton [this message]
2023-07-11 11:54 ` David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230710132611.ccf619f06f3ead06986cb7f4@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=kim.phillips@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=rostedt@goodmis.org \
--cc=yajun.deng@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox