From: jbarnes@sgi.com (Jesse Barnes)
To: Greg KH <greg@kroah.com>
Cc: Grant Grundler <grundler@parisc-linux.org>,
Matthew Wilcox <willy@debian.org>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
jeremy@sgi.com
Subject: Re: [RFC] Relaxed PIO read vs. DMA write ordering
Date: Wed, 7 Jan 2004 15:56:33 -0800 [thread overview]
Message-ID: <20040107235633.GA7312@sgi.com> (raw)
In-Reply-To: <20040107232754.GA2807@kroah.com>
On Wed, Jan 07, 2004 at 03:27:54PM -0800, Greg KH wrote:
> On Wed, Jan 07, 2004 at 03:07:12PM -0800, Jesse Barnes wrote:
> >
> > 1) add pcix_enable_relaxed() and read_relaxed() (read() would always be
> > ordered)
>
> This probably preserves the current situation best, enabling driver
> writers to be explicit in knowing what is happening.
That's what I figured too. It also seems like it has the lowest
probability of introducing PIO vs. DMA races, since you have to
explicitly change a read() call.
What about compatibility though? How should the interface behave if
it's accessing a PCI-X device that happens to be in PCI mode? Ideally,
we could add these calls in and introduce no penalty for platforms that
don't support it...
Thanks,
Jesse
next prev parent reply other threads:[~2004-01-07 23:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 17:58 [RFC] Relaxed PIO read vs. DMA write ordering Jesse Barnes
2004-01-07 19:02 ` Matthew Wilcox
2004-01-07 22:21 ` Grant Grundler
2004-01-07 23:07 ` Jesse Barnes
2004-01-07 23:27 ` Greg KH
2004-01-07 23:56 ` Jesse Barnes [this message]
2004-01-08 0:34 ` Jesse Barnes
2004-01-08 0:08 ` Jeremy Higdon
2004-01-08 10:01 ` Jes Sorensen
2004-01-08 6:38 ` Grant Grundler
2004-01-08 16:23 ` Leonid Grossman
2004-01-08 17:39 ` Jesse Barnes
2004-01-08 17:54 ` Christoph Hellwig
2004-01-08 19:48 ` Leonid Grossman
2004-01-08 17:36 ` Jesse Barnes
2004-01-08 18:44 ` Grant Grundler
2004-01-09 7:13 ` Jeremy Higdon
2004-01-09 19:51 ` Jesse Barnes
2004-01-09 23:15 ` Jesse Barnes
2004-01-09 20:02 ` Grant Grundler
2004-01-11 14:34 ` James Bottomley
2004-01-09 7:39 ` Jochen Friedrich
2004-01-09 20:27 ` Grant Grundler
2004-01-09 22:12 ` Ivan Kokshaysky
2004-01-07 22:58 ` Jesse Barnes
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=20040107235633.GA7312@sgi.com \
--to=jbarnes@sgi.com \
--cc=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=jeremy@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=willy@debian.org \
/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.