From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64 implementation of lib/iomap.c
Date: Tue, 26 Oct 2004 17:49:07 +0000 [thread overview]
Message-ID: <200410261049.07181.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <16759.51459.598187.91726@napali.hpl.hp.com>
On Tuesday, October 26, 2004 10:06 am, Linus Torvalds wrote:
> On Tue, 26 Oct 2004, Jesse Barnes wrote:
> > I'm pretty sure this is the case. In fact when I last discussed this
> > with Linus he indicated that an ioread shouldn't guarantee DMA completion
> > either, which would mean we could reuse the read_relaxed stuff to
> > implement it.
>
> .. but other people disagreed with me. I think the consensus was that DMA
> completion _should_ be honoured, but if SGI knows that their machines are
> not doing it right, and take on the responsibility for fixing drivers,
> that's _their_ problem. You only need to care about a few drivers, after
> all.
>
> In short, I think of that DMA completion issue as a SGI-private
> optimization, and _not_ a general rule.
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. Since PCI-X and PCI-Express have optional relaxed
semantics that might make sense...
Thanks,
Jesse
next prev parent reply other threads:[~2004-10-26 17:49 UTC|newest]
Thread overview: 15+ 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 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 [this message]
2004-10-26 17:55 ` Grant Grundler
2004-10-26 18:05 ` Grant Grundler
2004-10-26 18:12 ` Grant Grundler
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=200410261049.07181.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox