From: Segher Boessenkool <segher@kernel.crashing.org>
To: paulmck@linux.vnet.ibm.com
Cc: heiko.carstens@de.ibm.com, horms@verge.net.au,
linux-kernel@vger.kernel.org, rpjday@mindspring.com, ak@suse.de,
netdev@vger.kernel.org, cfriesen@nortel.com,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
Nick Piggin <nickpiggin@yahoo.com.au>,
linux-arch@vger.kernel.org, jesper.juhl@gmail.com, zlynx@acm.org,
schwidefsky@de.ibm.com, Chris Snook <csnook@redhat.com>,
davem@davemloft.net, wensong@linux-vs.org, wjiang@resilience.com,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 6/24] make atomic_read() behave consistently on frv
Date: Wed, 15 Aug 2007 23:15:51 +0200 [thread overview]
Message-ID: <7131d547746a998fcec74d1c091f9f6a@kernel.crashing.org> (raw)
In-Reply-To: <20070815203836.GO9645@linux.vnet.ibm.com>
> Please check the definition of "cache coherence".
Which of the twelve thousand such definitions? :-)
> Summary: the CPU is indeed within its rights to execute loads and
> stores
> to a single variable out of order, -but- only if it gets the same
> result
> that it would have obtained by executing them in order. Which means
> that
> any reordering of accesses by a single CPU to a single variable will be
> invisible to the software.
I'm still not sure if that applies to all architectures.
Doesn't matter anyway, let's kill this thread :-)
Segher
next prev parent reply other threads:[~2007-08-15 21:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 13:41 [PATCH 6/24] make atomic_read() behave consistently on frv Chris Snook
2007-08-09 16:54 ` Chris Snook
2007-08-10 9:23 ` David Howells
2007-08-10 19:54 ` Chris Snook
2007-08-11 0:54 ` Herbert Xu
2007-08-11 4:29 ` Paul E. McKenney
2007-08-13 5:15 ` Herbert Xu
2007-08-13 6:03 ` Paul E. McKenney
2007-08-14 5:34 ` Nick Piggin
2007-08-14 7:26 ` Herbert Xu
2007-08-14 17:01 ` Paul E. McKenney
2007-08-14 22:01 ` Arnd Bergmann
2007-08-14 22:43 ` Paul E. McKenney
2007-08-15 13:29 ` Arnd Bergmann
2007-08-15 15:06 ` Michael Buesch
2007-08-15 13:30 ` Nick Piggin
2007-08-15 20:15 ` Paul E. McKenney
2007-08-16 1:09 ` Nick Piggin
2007-08-16 2:27 ` Paul E. McKenney
2007-08-11 8:47 ` David Howells
2007-08-13 6:44 ` Chris Snook
2007-08-14 5:42 ` Nick Piggin
2007-08-15 18:51 ` Segher Boessenkool
2007-08-15 19:18 ` Paul E. McKenney
2007-08-15 19:46 ` Segher Boessenkool
2007-08-15 19:59 ` Paul E. McKenney
2007-08-15 20:13 ` Segher Boessenkool
2007-08-15 20:38 ` Paul E. McKenney
2007-08-15 21:15 ` Segher Boessenkool [this message]
2007-08-16 1:20 ` Nick Piggin
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=7131d547746a998fcec74d1c091f9f6a@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=cfriesen@nortel.com \
--cc=csnook@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=horms@verge.net.au \
--cc=jesper.juhl@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rpjday@mindspring.com \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=wensong@linux-vs.org \
--cc=wjiang@resilience.com \
--cc=zlynx@acm.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;
as well as URLs for NNTP newsgroup(s).