From: Christoph Hellwig <hch@lst.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Christoph Hellwig <hch@lst.de>,
Dave Hansen <dave.hansen@intel.com>,
Georgi Djakov <quic_c_gdjako@quicinc.com>,
catalin.marinas@arm.com, will@kernel.org,
dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, m.szyprowski@samsung.com, robin.murphy@arm.com,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, djakov@kernel.org
Subject: Re: [RFC] mm: Allow ZONE_DMA32 to be disabled via kernel command line
Date: Fri, 27 Jan 2023 08:07:05 +0100 [thread overview]
Message-ID: <20230127070705.GA4180@lst.de> (raw)
In-Reply-To: <C7DCCCB1-AABE-4D3B-80B1-AB755A68D460@zytor.com>
On Thu, Jan 26, 2023 at 10:52:43PM -0800, H. Peter Anvin wrote:
> >If people want ZONE_DMA32 to go away we need something to replace
> >it first, like a large enough CMA region in the 32-bit addressable
> >range.
>
> Not to mention all kinds of odd masks like 30, 31, 39, 40, 46, ... bits.
Yes. Out of those all >= 32 are falling straight into ZONE_DM32,
the lower ones we do a first try in ZONE_DMA32 and then fall back to
ZONE_DMA. <= 29 mask OTOH are really rate in modern systems for
actual devices. So with a CMA region for what is currently ZONE_DMA
and one for the first 1G we'd probably cover most of what's actually
needed for x86_64. Of course on 32-bit architetures things become
a lot more complicated due to highmem.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-27 7:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 16:43 [RFC] mm: Allow ZONE_DMA32 to be disabled via kernel command line Georgi Djakov
2023-01-26 18:51 ` Dave Hansen
2023-01-26 22:56 ` Georgi Djakov
2023-01-27 0:57 ` Randy Dunlap
2023-01-27 6:35 ` Christoph Hellwig
2023-01-27 6:52 ` H. Peter Anvin
2023-01-27 7:07 ` Christoph Hellwig [this message]
2023-01-26 19:15 ` Robin Murphy
2023-01-27 2:20 ` Chris Goldsworthy
2023-01-27 8:55 ` Hillf Danton
2023-02-01 4:09 ` Chris Goldsworthy
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=20230127070705.GA4180@lst.de \
--to=hch@lst.de \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=djakov@kernel.org \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quic_c_gdjako@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox