lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 22 Mar 2019 13:09:26 -0700 From: Nicolin Chen <nicoleotsuka@...il.com> To: Catalin Marinas <catalin.marinas@....com> Cc: hch@....de, robin.murphy@....com, vdumpa@...dia.com, will.deacon@....com, chris@...kel.net, jcmvbkbc@...il.com, joro@...tes.org, dwmw2@...radead.org, m.szyprowski@...sung.com, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, linux-xtensa@...ux-xtensa.org, iommu@...ts.linux-foundation.org, jonathanh@...dia.com Subject: Re: [PATCH v2 RFC/RFT] dma-contiguous: Get normal pages for single-page allocations Hi Catalin, On Fri, Mar 22, 2019 at 10:57:13AM +0000, Catalin Marinas wrote: > > > Do you have any numbers to back this up? You don't seem to address > > > dma_direct_alloc() either but, as I said above, it's not trivial since > > > some platforms expect certain physical range for DMA allocations. > > > > What's the dma_direct_alloc() here about? Mind elaborating? > > I just did a grep for dma_alloc_from_contiguous() in the 5.1-rc1 kernel > and came up with __dma_direct_alloc_pages(). Should your patch cover > this as well? I don't get the meaning of "cover this" here. What missing part do you refer to?
Powered by blists - more mailing lists