lkml.org 
[lkml]   [2013]   [Aug]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Documentation/memory-barriers: fix a error that mistakes a CPU notion in Section Transitivity
On 08/27/2013 05:34:22 AM, larmbr wrote:
> The memory-barriers document may has a error in Section TRANSITIVITY.
>
> For transitivity, see a example below, given that
>
> * CPU 2's load from X follows CPU 1's store to X, and
> CPU 2's load from Y preceds CPU 3's store to Y.

I'd prefer somebody with a better understanding of this code review it
before merging. I'm not a memory barrier semantics expert, I can't tell
you if this _is_ a bug.

> +The key point is that CPU 1's storing 1 to X preceds CPU 2's loading
> 1

precedes

> +from X, and CPU 2's loading 0 from Y preceds CPU 3's storing 1 to Y,

precedes

> +which implies a ordering that the general barrier in CPU 2
> guarantees:

an ordering

> +all store and load operations must happen before those after the
> barrier
> +with respect to view of CPU 3, which constrained by a general
> barrier, too.

the view of (or possibly "from the point of view of", the current
phrasing is awkward)

which is constrained

Rob

\
 
 \ /
  Last update: 2013-08-31 06:21    [W:1.733 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site