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
| ||
|
Date: Wed, 19 Mar 2008 17:32:58 -0700 From: akepner@....com To: Michael Ellerman <michael@...erman.id.au> Cc: James Bottomley <James.Bottomley@...senPartnership.com>, Grant Grundler <grundler@...isc-linux.org>, Tony Luck <tony.luck@...el.com>, Jesse Barnes <jbarnes@...tuousgeek.org>, Jes Sorensen <jes@....com>, Randy Dunlap <randy.dunlap@...cle.com>, Roland Dreier <rdreier@...co.com>, David Miller <davem@...emloft.net>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, linux-kernel@...r.kernel.org, Mark Nelson <mdnelson@....ibm.com> Subject: Re: [PATCH 1/3 v3] dma: document dma_{un}map_{single|sg}_attrs() interface On Fri, Mar 14, 2008 at 03:30:29PM +1100, Michael Ellerman wrote: > > I like this better, sorry to keep nitpicking, but just a few comments > below .. Comments are appreciated. > ... > You say a "DMA to a memory region with the DMA_ATTR_BARRIER attribute > forces all pending DMA writes to complete". Does it force _all_ DMA > writes to complete, or just writes to the region, or just writes coming > from devices? What if something is writing to a device? > Yes, forces all writes to complete (as others have already said). > Does DMA_ATTR_BARRIER have any effect on reads? > No, changed the name to DMA_ATTR_WRITE_BARRIER to emphasize this. -- Arthur -- 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