From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64 implementation of lib/iomap.c
Date: Tue, 26 Oct 2004 18:12:58 +0000 [thread overview]
Message-ID: <20041026181258.GH2728@cup.hp.com> (raw)
In-Reply-To: <16759.51459.598187.91726@napali.hpl.hp.com>
On Tue, Oct 26, 2004 at 10:49:07AM -0700, Jesse Barnes wrote:
> What about the relaxed read then? Should we have ioread_relaxed?
> I thought we had agreed that it was easier to assume relaxed semantics
> for ioread and add a dma_sync interface.
I would expect that requires fixing PCI drivers that depend on it.
Adding a dma_sync interface would probably make it easier to support
non-coherent (DMA and CPU caches are not coherent) platforms.
> Since PCI-X and PCI-Express have optional relaxed semantics that
> might make sense...
Jesse, you keep mixing up PCI-X Relaxed Ordering with readX() interface
and the two are NOT (directly) related.
The device driver can enable PCI-X Relaxed Ordering hints in general.
But the IO device controls "RO" hint use on individual bus transactions
it masters.
I'm not sure about PCI-Express (whole new bus protocol).
grant
next prev parent reply other threads:[~2004-10-26 18:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 14:34 ia64 implementation of lib/iomap.c David Mosberger
2004-10-21 17:34 ` Bjorn Helgaas
2004-10-21 17:38 ` David Mosberger
2004-10-25 16:48 ` Bjorn Helgaas
2004-10-26 7:48 ` David Mosberger
2004-10-26 15:21 ` Linus Torvalds
2004-10-26 15:21 ` Linus Torvalds
2004-10-26 16:26 ` David Mosberger
2004-10-26 16:26 ` David Mosberger
2004-10-26 16:23 ` Jesse Barnes
2004-10-26 17:06 ` Linus Torvalds
2004-10-26 17:49 ` Jesse Barnes
2004-10-26 17:55 ` Grant Grundler
2004-10-26 18:05 ` Grant Grundler
2004-10-26 18:12 ` Grant Grundler [this message]
2004-10-26 18:19 ` Jesse Barnes
2004-10-26 18:37 ` 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=20041026181258.GH2728@cup.hp.com \
--to=iod00d@hp.com \
--cc=linux-ia64@vger.kernel.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.