From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>,
Feng Tang <feng.tang@linux.alibaba.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Ying Huang <ying.huang@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Liam.Howlett@oracle.com, Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, Christoph Hellwig <hch@lst.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Changrong Chen <chenchangrong.ccr@alibaba-inc.com>
Subject: Re: [PATCH v3] dma-contiguous: setup default numa cma area if not configured explicitly
Date: Fri, 8 May 2026 22:57:15 +0200 [thread overview]
Message-ID: <1abedb3a-f162-42b8-91d4-7d1b3df43fff@kernel.org> (raw)
In-Reply-To: <59d05fdb-bb61-4d92-8df3-45aa3f9f7bee@arm.com>
On 5/8/26 14:58, Robin Murphy wrote:
> On 2026-05-08 12:46 pm, David Hildenbrand (Arm) wrote:
>> On 5/6/26 17:46, Feng Tang wrote:
>>>
>>> Yes, it is confusing.
>>>
>>>
>>> Maybe a CMA_NUMA_SIZE_MBYTES?
>>
>> Maybe, I'm hoping some CMA DMA people have the capacity to provide input.
>
> But really that _is_ pretty much the idea here
Cool, I guess that's the right direction then, thanks.
--
Cheers,
David
next prev parent reply other threads:[~2026-05-08 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 6:05 [PATCH v3] dma-contiguous: setup default numa cma area if not configured explicitly Feng Tang
2026-04-28 7:52 ` David Hildenbrand (Arm)
2026-04-28 8:37 ` Feng Tang
2026-04-28 9:03 ` Feng Tang
2026-05-01 18:51 ` David Hildenbrand (Arm)
2026-05-06 15:46 ` Feng Tang
2026-05-08 11:46 ` David Hildenbrand (Arm)
2026-05-08 12:58 ` Robin Murphy
2026-05-08 20:57 ` David Hildenbrand (Arm) [this message]
2026-05-01 5:57 ` kernel test robot
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=1abedb3a-f162-42b8-91d4-7d1b3df43fff@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=chenchangrong.ccr@alibaba-inc.com \
--cc=feng.tang@linux.alibaba.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mhocko@suse.com \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=will@kernel.org \
--cc=ying.huang@linux.alibaba.com \
/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