[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1804271136030.11686@nuc-kabylake>
Date: Fri, 27 Apr 2018 11:36:23 -0500 (CDT)
From: Christopher Lameter <cl@...ux.com>
To: Matthew Wilcox <willy@...radead.org>
cc: Michal Hocko <mhocko@...nel.org>,
Christoph Hellwig <hch@...radead.org>,
"Luis R. Rodriguez" <mcgrof@...nel.org>, linux-mm@...ck.org,
Jan Kara <jack@...e.cz>, matthew@....cx, x86@...nel.org,
luto@...capital.net, martin.petersen@...cle.com,
jthumshirn@...e.de, broonie@...nel.org, linux-spi@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
"lsf-pc@...ts.linux-foundation.org"
<lsf-pc@...ts.linux-foundation.org>
Subject: Re: [LSF/MM TOPIC NOTES] x86 ZONE_DMA love
On Fri, 27 Apr 2018, Matthew Wilcox wrote:
> Some devices have incredibly bogus hardware like 28 bit addressing
> or 39 bit addressing. We don't have a good way to allocate memory by
> physical address other than than saying "GFP_DMA for anything less than
> 32, GFP_DMA32 (or GFP_KERNEL on 32-bit) for anything less than 64 bit".
>
> Even CMA doesn't have a "cma_alloc_phys()". Maybe that's the right place
> to put such an allocation API.
The other way out of this would be to require a IOMMU?
Powered by blists - more mailing lists