| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100921163456.7e2c9b32@udp111988uds.am.freescale.net> Date: Tue, 21 Sep 2010 16:34:56 -0500 From: Scott Wood <scottwood@...escale.com> To: Timur Tabi <timur.tabi@...il.com> CC: Kumar Gala <galak@...nel.crashing.org>, dan.j.williams@...el.com, linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] fsldma: add support to 36-bit physical address On Tue, 21 Sep 2010 16:24:10 -0500 Timur Tabi <timur.tabi@...il.com> wrote: > On Tue, Sep 21, 2010 at 7:55 AM, Kumar Gala <galak@...nel.crashing.org> wrote: > > > > On Sep 21, 2010, at 5:57 AM, Li Yang wrote: > > > >> Signed-off-by: Li Yang <leoli@...escale.com> > >> --- > > > > We really should have a sentence about how or why this works to address 36-bit addressing. > > For example, I would like to know which memory is going to be > allocated above 4GB. I don't know much about the kernel's async > library, but my understanding is that fsldma does not allocate any of > the memory buffers that it copies data to/from. This doesn't control allocation (it probably should with dma_alloc_coherent, though I don't see it in the code), it controls whether swiotlb will create a bounce buffer -- defeating the point of using DMA to accelerate a memcpy. -Scott -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists