From: Daniel Phillips <phillips@bonn-fries.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>, Keith Owens <kaos@ocs.com.au>
Cc: Jesse Barnes <jbarnes@sgi.com>,
David Mosberger <davidm@hpl.hp.com>, Dan Maas <dmaas@dcine.com>,
<linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Ben Collins <bcollins@debian.org>
Subject: Re: readl/writel and memory barriers
Date: Sat, 23 Feb 2002 05:48:26 +0100 [thread overview]
Message-ID: <E16eU6m-0002Ga-00@starship.berlin> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0202201627270.3312-100000@dragon.pdx.osdl.net>
In-Reply-To: <Pine.LNX.4.33L2.0202201627270.3312-100000@dragon.pdx.osdl.net>
On February 21, 2002 01:29 am, Randy.Dunlap wrote:
> On Wed, 20 Feb 2002, Keith Owens wrote:
> | Ignoring the issue of hardware that reorders I/O, volatile accesses
> | must not be reordered by the compiler. From a C9X draft (1999, anybody
> | have the current C standard online?) :-
> PDF file, for about US$18 - US$20, downloaded from ISO.
The drafts are supposed to be public.
--
Daniel
next prev parent reply other threads:[~2002-02-25 3:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 1:45 readl/writel and memory barriers Dan Maas
2002-02-19 9:31 ` Alan Cox
2002-02-19 17:10 ` David Mosberger
2002-02-19 18:35 ` Jesse Barnes
2002-02-19 19:33 ` David Mosberger
2002-02-19 19:42 ` Jesse Barnes
2002-02-19 20:11 ` Dan Maas
2002-02-19 20:23 ` Jesse Barnes
2002-02-19 22:05 ` Keith Owens
2002-02-19 22:17 ` Jesse Barnes
2002-02-21 0:29 ` Randy.Dunlap
2002-02-23 4:48 ` Daniel Phillips [this message]
2002-02-25 16:19 ` Randy.Dunlap
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=E16eU6m-0002Ga-00@starship.berlin \
--to=phillips@bonn-fries.net \
--cc=bcollins@debian.org \
--cc=benh@kernel.crashing.org \
--cc=davidm@hpl.hp.com \
--cc=dmaas@dcine.com \
--cc=jbarnes@sgi.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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.