From: "David S. Miller" <davem@redhat.com>
To: jgarzik@pobox.com
Cc: benh@kernel.crashing.org, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [RFC] {read,write}s{b,w,l} or iobarrier_*()
Date: Thu, 26 Sep 2002 14:12:23 -0700 (PDT) [thread overview]
Message-ID: <20020926.141223.128110378.davem@redhat.com> (raw)
In-Reply-To: <3D93348D.3060304@pobox.com>
From: Jeff Garzik <jgarzik@pobox.com>
Date: Thu, 26 Sep 2002 12:23:41 -0400
Benjamin Herrenschmidt wrote:
> - Have all archs provide {read,write}s{b,w,l} functions.
> Those will hide all of the details of bytewapping & barriers
> from the drivers and can be used as-is for things like IDE
> MMIO iops.
I prefer this solution...
I'm starting to think about taking back all the previous
arguments I had against this idea. It's starting to sound
like the preferred way to go.
next prev parent reply other threads:[~2002-09-26 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 15:59 [RFC] {read,write}s{b,w,l} or iobarrier_*() Benjamin Herrenschmidt
2002-09-26 16:23 ` Jeff Garzik
2002-09-26 21:12 ` David S. Miller [this message]
2002-09-27 6:21 ` Andre Hedrick
2002-09-27 9:59 ` Benjamin Herrenschmidt
2002-09-27 8:41 ` Geert Uytterhoeven
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=20020926.141223.128110378.davem@redhat.com \
--to=davem@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).