From: akepner@sgi.com
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Grant Grundler <grundler@parisc-linux.org>,
Michael Ellerman <michael@ellerman.id.au>,
Tony Luck <tony.luck@intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Jes Sorensen <jes@sgi.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Roland Dreier <rdreier@cisco.com>,
David Miller <davem@davemloft.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3 v3] dma: document dma_{un}map_{single|sg}_attrs() interface
Date: Wed, 5 Mar 2008 10:13:07 -0800 [thread overview]
Message-ID: <20080305181307.GR17802@sgi.com> (raw)
In-Reply-To: <1204310276.4003.48.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2008-03-05 18:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 3:24 [PATCH 1/3 v3] dma: document dma_{un}map_{single|sg}_attrs() interface akepner
2008-02-29 2:45 ` Michael Ellerman
2008-02-29 18:25 ` Grant Grundler
2008-02-29 18:37 ` James Bottomley
2008-03-01 2:56 ` Benjamin Herrenschmidt
2008-03-01 3:11 ` Jesse Barnes
2008-03-01 7:18 ` Grant Grundler
2008-03-05 18:13 ` akepner [this message]
2008-03-05 19:02 ` Jesse Barnes
2008-03-06 6:01 ` Michael Ellerman
2008-03-12 1:19 ` akepner
2008-03-14 4:13 ` Grant Grundler
2008-03-14 4:30 ` Michael Ellerman
2008-03-14 5:21 ` Grant Grundler
2008-03-14 16:40 ` Jesse Barnes
2008-03-18 1:08 ` Michael Ellerman
2008-03-20 0:32 ` akepner
2008-02-29 21:23 ` akepner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080305181307.GR17802@sgi.com \
--to=akepner@sgi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=grundler@parisc-linux.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=randy.dunlap@oracle.com \
--cc=rdreier@cisco.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.