From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: paulmck@linux.vnet.ibm.com, 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, 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: Thu, 16 Aug 2007 11:20:53 +1000 [thread overview]
Message-ID: <46C3A675.7050108@yahoo.com.au> (raw)
In-Reply-To: <7131d547746a998fcec74d1c091f9f6a@kernel.crashing.org>
Segher Boessenkool wrote:
>> Please check the definition of "cache coherence".
>
>
> Which of the twelve thousand such definitions? :-)
Every definition I have seen says that writes to a single memory
location have a serial order as seen by all CPUs, and that a read
will return the most recent write in the sequence (with a bit of
extra mumbo jumbo to cover store queues and store forwarding).
Within such a definition, I don't see how would be allowed for a
single CPU to execute reads out of order and have the second read
return an earlier write than the first read.
--
SUSE Labs, Novell Inc.
prev parent reply other threads:[~2007-08-16 1:21 UTC|newest]
Thread overview: 31+ 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 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
2007-08-16 1:20 ` Nick Piggin [this message]
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=46C3A675.7050108@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--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=paulmck@linux.vnet.ibm.com \
--cc=rpjday@mindspring.com \
--cc=schwidefsky@de.ibm.com \
--cc=segher@kernel.crashing.org \
--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 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.