public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Jes Sorensen <jes@sgi.com>,
	akepner@sgi.com, Randy Dunlap <randy.dunlap@oracle.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	rdreier@cisco.com, linux-ia64 <linux-ia64@vger.kernel.org>
Subject: Re: [PATCH 2/3] dma: override "dma_flags_set_dmaflush" for sn-ia64
Date: Wed, 22 Aug 2007 13:13:04 -0500	[thread overview]
Message-ID: <1187806384.3410.70.camel@localhost.localdomain> (raw)
In-Reply-To: <200708221017.11805.jbarnes@virtuousgeek.org>

On Wed, 2007-08-22 at 10:17 -0700, Jesse Barnes wrote:
> On Wednesday, August 22, 2007 10:04:32 am James Bottomley wrote:
> > The spec isn't ambiguous ... it says if the device and bridge agree on
> > relaxed ordering, then it *may* be observed in the transaction.  If
> > there's a disagreement or neither wishes to support relaxed ordering
> > then the transaction *must* be strict.
> 
> Arg, don't make me dig out my spec, I don't have it handy...

Well ... I don't have one either.  However, Grant Grundler did a
presentation to OLS about relaxed ordering, and I went over it pretty
thoroughly with him a while ago.  The bottom line is that the default is
always strict unless both the bridge and the device agree otherwise.

> > I really don't think a work around for a PCI spec violation belongs in
> > the generic DMA code, do you?  The correct fix for this should be to set
> > the device hints to strict ordering, which presumably altix respects?
> 
> Well, the Altix hw by itself won't honor device hints (I'm not even sure if 
> there are devices that honor order hints like you outline above).  However, 
> Altix could track per-device ordering as long as arch code was called from 
> such a hook.
> 
> > In which case, it sounds like what needs exposing are access to the PCI
> > device hints.  I believe both PCI-X and PCIe have these hints as
> > optional specifiers in the bridges, so it should be in a current Rev of
> > the PCI spec.  Or are you proposing adding an additional PCI API that
> > allows transaction flushes to be inserted into the stream for devices
> > and bridges that have already negotiated relaxed ordering? ... in which
> > case we need to take this to the PCI list.
> 
> I think it would have to be the latter, since otherwise it would be hard to 
> setup just completion queue requests to be ordered.

OK ... I think this is definitely a PCI specific API ... and probably a
generic one for requesting order flushes in devices that have negotiated
relaxed ordering.  Do you want to start a new thread on linux-pci and cc
me?

James



  reply	other threads:[~2007-08-22 18:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-18  0:27 [PATCH 2/3] dma: override "dma_flags_set_dmaflush" for sn-ia64 akepner
2007-08-20  8:24 ` Jes Sorensen
2007-08-20 16:07   ` akepner
2007-08-21 19:35   ` akepner
2007-08-21 20:05     ` Randy Dunlap
2007-08-21 20:55       ` James Bottomley
2007-08-22  0:34         ` akepner
2007-08-22  1:14           ` James Bottomley
2007-08-22  7:39             ` Jes Sorensen
2007-08-22 14:02               ` James Bottomley
2007-08-22 16:03                 ` Jesse Barnes
2007-08-22 16:44                   ` James Bottomley
2007-08-22 16:51                     ` Jesse Barnes
2007-08-22 17:04                       ` James Bottomley
2007-08-22 17:03                         ` Jes Sorensen
2007-08-22 18:10                           ` James Bottomley
2007-08-23  8:45                             ` Jes Sorensen
2007-08-22 17:17                         ` Jesse Barnes
2007-08-22 18:13                           ` James Bottomley [this message]
2007-08-22 18:44                             ` akepner
2007-08-23  5:58               ` Jeremy Higdon
2007-08-22 15:54             ` akepner
2007-08-21 20:16     ` Matthew Wilcox
2007-08-21 21:37       ` akepner
2007-08-22  7:44       ` Jes Sorensen

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=1187806384.3410.70.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akepner@sgi.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jes@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rdreier@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox