From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Graf (AWS), Alexander" <graf@amazon.de>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Robin Murphy <robin.murphy@arm.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
"nh-open-source@amazon.com" <nh-open-source@amazon.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
The AWS Nitro Enclaves Team <aws-nitro-enclaves-devel@amazon.com>
Subject: Re: [PATCH v2] dma-contiguous: support percentage sizes in cma_pernuma= and numa_cma=
Date: Fri, 20 Nov 2026 15:12:41 -0400 [thread overview]
Message-ID: <20261120191241.GD1133597@ziepe.ca> (raw)
In-Reply-To: <28a0f946-af4e-497f-a923-f11b79d94930@amazon.com>
On Thu, Nov 19, 2026 at 12:27:08PM +0000, Graf (AWS), Alexander wrote:
> Ideally all of this would be policy that only takes effect later at
> boot, so that we don't require pre-boot logic or a reboot. For this to
> work, we would need to have Linux restrict its memory allocations to a
> small'ish region instead of spreading them, maybe to the KHO scratch
> region, or maybe by favoring allocations in phys addr order. At least
> until the boot is at a point where you could perform the allocation. And
> then we would also have large physically contiguous blocks available to
> allocate from and potentially change the tag to CMA.
That actually seems like a sort of reasonable idea...
What about the reverse, you boot with a huge CMA and then shrink it in
the initrd to what you really want? For this you'd just want some
command line indicating how much non-CMA memory to have, which should
be fairly predictable to get into the initrd?
Jason
prev parent reply other threads:[~2026-11-20 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261114145340eucas1p2f7699b88eae34f7904cf68109dc3eb4f@eucas1p2.samsung.com>
2026-11-14 14:53 ` [PATCH v2] dma-contiguous: support percentage sizes in cma_pernuma= and numa_cma= Alexander Graf
2026-11-19 11:19 ` Marek Szyprowski
2026-11-19 12:27 ` Graf (AWS), Alexander
2026-11-20 19:12 ` Jason Gunthorpe [this message]
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=20261120191241.GD1133597@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=akpm@linux-foundation.org \
--cc=aws-nitro-enclaves-devel@amazon.com \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=graf@amazon.de \
--cc=iommu@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=nh-open-source@amazon.com \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.