linux-kernel - Re: [PATCH 1/3 v3] dma: document dma_{un}map_{single|sg}

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 5 Mar 2008 10:13:07 -0800
From:	akepner@....com
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	Grant Grundler <grundler@...isc-linux.org>,
	Michael Ellerman <michael@...erman.id.au>,
	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
Subject: Re: [PATCH 1/3 v3] dma: document dma_{un}map_{single|sg}_attrs() interface

On Fri, Feb 29, 2008 at 12:37:56PM -0600, James Bottomley wrote:
> ....
> To be honest, I still don't like the name.  SYNC_ON_WRITE is the SN2
> implementation.  What it's actually doing is implementing strict
> ordering semantics.  I think it should really be
> DMA_ATTR_STRICT_ORDERING (with a corresponding
> DMA_ATTR_RELAXED_ORDERING)....

I've been thinking about a new name, but don't like 
DMA_ATTR_STRICT_ORDERING. 

What I'm trying to do is to establish order (across 
a NUMA fabric) of DMA to different memory regions, i.e., 
DMA to memory region A forces all outstanding DMA (to 
memory regions B, C,....) to complete first.

DMA_ATTR_STRICT_ORDERING sounds like a PCI thing to me, 
and this is a NUMA interconnect thing.

-- 
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/