From: "David S. Miller" <davem@redhat.com>
To: andre@linux-ide.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: readsw/writesw readsl/writesl
Date: Mon, 26 Aug 2002 23:43:23 -0700 (PDT) [thread overview]
Message-ID: <20020826.234323.39328052.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10208262321150.24156-100000@master.linux-ide.org>
From: Andre Hedrick <andre@linux-ide.org>
Date: Mon, 26 Aug 2002 23:23:22 -0700 (PDT)
Would you consider these for each arch as there are coresponding one for
IOMIO, and life would be better if we had a standard set for MMIO.
Please consider the request.
I responded to the private email I got on this subject.
I forget who asked me this, but they said they were working
on this IDE stuff.
My response was that io_barrier() shall be defined on all
platforms in asm/io.h and that you can then define your
ide_read{l,w,b} as:
__raw_raw{l,w,b}(...);
io_barrier();
So instead of having a million read* variations, we have one that is
standard usage (little endian + I/O barrier) and then a raw variant
where the cpu does nothing special and you have to byte-twiddle and
barrier explicitly.
next prev parent reply other threads:[~2002-08-27 6:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 20:52 [BKPATCH] Read-Copy Update 2.5 Dipankar Sarma
2002-08-27 0:24 ` Rusty Russell
2002-08-27 6:11 ` Dipankar Sarma
2002-08-27 6:11 ` David S. Miller
2002-08-27 6:23 ` readsw/writesw readsl/writesl Andre Hedrick
2002-08-27 6:43 ` David S. Miller [this message]
2002-08-27 6:55 ` Andre Hedrick
2002-08-27 7:30 ` David S. Miller
2002-08-27 6:46 ` Benjamin Herrenschmidt
2002-08-27 6:49 ` Benjamin Herrenschmidt
2002-08-27 17:25 ` Alan Cox
2002-08-27 21:31 ` David S. Miller
2002-08-27 13:58 ` [BKPATCH] Read-Copy Update 2.5 Dipankar Sarma
-- strict thread matches above, loose matches on Subject: below --
2002-08-27 16:00 readsw/writesw readsl/writesl Richard.Zidlicky
2002-08-27 9:29 ` Benjamin Herrenschmidt
2002-08-28 12:23 ` Richard Zidlicky
2002-08-28 16:17 ` Benjamin Herrenschmidt
2002-08-29 9:17 ` Richard Zidlicky
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=20020826.234323.39328052.davem@redhat.com \
--to=davem@redhat.com \
--cc=andre@linux-ide.org \
--cc=linux-kernel@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