From: jbarnes@sgi.com (Jesse Barnes)
To: Grant Grundler <iod00d@hp.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, jeremy@sgi.com
Subject: Re: [PATCH] readX_relaxed interface
Date: Thu, 15 Jan 2004 22:56:58 +0000 [thread overview]
Message-ID: <20040115225658.GA9389@sgi.com> (raw)
In-Reply-To: <20040115221640.GA11283@cup.hp.com>
On Thu, Jan 15, 2004 at 02:16:40PM -0800, Grant Grundler wrote:
> Outside the context of PCI-X Relaxed Ordering, this violates PCI
> ordering rules. Any patches to drivers *using* the new readb()
> variants in effect work around this violation. I"m ok with that - just
> want it to be clear.
Yep, that's an advantage of this API--you only use it when you know it's
ok to violate those rules.
> PCI-X support will need a different interface
> (eg pcix_enable_relaxed_ordering()) to support
> it's form of "Relaxed Ordering".
Right, seperate issue.
> > If it looks ok, I'll add in macros for the other arches and send it out
> > for inclusion.
>
> It looks ok to me.
Great, thanks.
Jesse
WARNING: multiple messages have this Message-ID (diff)
From: jbarnes@sgi.com (Jesse Barnes)
To: Grant Grundler <iod00d@hp.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, jeremy@sgi.com
Subject: Re: [PATCH] readX_relaxed interface
Date: Thu, 15 Jan 2004 14:56:58 -0800 [thread overview]
Message-ID: <20040115225658.GA9389@sgi.com> (raw)
In-Reply-To: <20040115221640.GA11283@cup.hp.com>
On Thu, Jan 15, 2004 at 02:16:40PM -0800, Grant Grundler wrote:
> Outside the context of PCI-X Relaxed Ordering, this violates PCI
> ordering rules. Any patches to drivers *using* the new readb()
> variants in effect work around this violation. I"m ok with that - just
> want it to be clear.
Yep, that's an advantage of this API--you only use it when you know it's
ok to violate those rules.
> PCI-X support will need a different interface
> (eg pcix_enable_relaxed_ordering()) to support
> it's form of "Relaxed Ordering".
Right, seperate issue.
> > If it looks ok, I'll add in macros for the other arches and send it out
> > for inclusion.
>
> It looks ok to me.
Great, thanks.
Jesse
next prev parent reply other threads:[~2004-01-15 22:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 20:49 [PATCH] readX_relaxed interface Jesse Barnes
2004-01-15 20:49 ` Jesse Barnes
2004-01-15 22:16 ` Grant Grundler
2004-01-15 22:16 ` Grant Grundler
2004-01-15 22:56 ` Jesse Barnes [this message]
2004-01-15 22:56 ` Jesse Barnes
2004-01-16 3:19 ` Jeremy Higdon
2004-01-16 3:19 ` Jeremy Higdon
2004-01-16 0:32 ` Greg KH
2004-01-16 0:32 ` Greg KH
2004-01-16 2:21 ` Jesse Barnes
2004-01-16 2:21 ` Jesse Barnes
2004-01-16 5:00 ` Linus Torvalds
2004-01-16 5:00 ` Linus Torvalds
2004-01-16 17:21 ` Jesse Barnes
2004-01-16 17:21 ` Jesse Barnes
2004-01-16 5:00 ` Grant Grundler
2004-01-16 5:00 ` Grant Grundler
2004-01-19 9:31 ` Hironobu Ishii
2004-01-19 9:31 ` Hironobu Ishii
2004-01-19 18:18 ` Grant Grundler
2004-01-19 18:18 ` Grant Grundler
2004-01-16 5:50 ` Grant Grundler
2004-01-16 5:50 ` Grant Grundler
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=20040115225658.GA9389@sgi.com \
--to=jbarnes@sgi.com \
--cc=iod00d@hp.com \
--cc=jeremy@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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.