Skip to contentSkip to conversation

Documentation/memory-barriers.txt: match table to its comment followed

PATCH In review Yao Dongdong 2 participants 3 messages Sep 16, 2014

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Documentation/memory-barriers.txt: match table to its comment followed

The table shows CPU2's sequence of events as "x = B; y = A;", but its comment followed described as "x = A; y = B;".

---
 Documentation/memory-barriers.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/memory-barriers.txt +2 -2
index a4de88f..9a46bbe 100644
@@ -115,8 +115,8 @@ For example, consider the following sequence of events:
        CPU 1           CPU 2
        =============== ===============
        { A == 1; B == 2 }
-       A = 3;          x = B;
-       B = 4;          y = A;
+       A = 3;          x = A;
+       B = 4;          y = B;
 
 The set of accesses as seen by the memory system in the middle can be arranged
 in 24 different combinations:

--
1.8.0.1

#1 lore raw

Hi,

Some one has submitted a patch addressing this issue a few days ago. The patch is now being cooked in the paulk's tree now, IIRC.

Thanks,
Jianyu Zhan

Quoted 31 lines · Yao Dongdong

The table shows CPU2's sequence of events as "x = B; y = A;", but its comment followed described as "x = A; y = B;".

---
 Documentation/memory-barriers.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/memory-barriers.txt +2 -3
index a4de88f..9a46bbe 100644
@@ -115,8 +115,8 @@ For example, consider the following sequence of events:
        CPU 1           CPU 2
        =============== ===============
        { A == 1; B == 2 }
-       A = 3;          x = B;
-       B = 4;          y = A;
+       A = 3;          x = A;
+       B = 4;          y = B;
 
 The set of accesses as seen by the memory system in the middle can be arranged
 in 24 different combinations:
--

1.8.0.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw
Quoted 8 lines · Jianyu Zhan

Hi,

Some one has submitted a patch addressing this issue a few days ago. The patch is now being cooked in the paulk's tree now, IIRC.

Thanks,
Jianyu Zhan

I have found the patch you mentioned.

Thanks

Quoted 32 lines · Yao Dongdong
Quoted 31 lines

The table shows CPU2's sequence of events as "x = B; y = A;", but its comment followed described as "x = A; y = B;".

---
 Documentation/memory-barriers.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/memory-barriers.txt +2 -3
index a4de88f..9a46bbe 100644
@@ -115,8 +115,8 @@ For example, consider the following sequence of events:
        CPU 1           CPU 2
        =============== ===============
        { A == 1; B == 2 }
-       A = 3;          x = B;
-       B = 4;          y = A;
+       A = 3;          x = A;
+       B = 4;          y = B;
 
 The set of accesses as seen by the memory system in the middle can be arranged
 in 24 different combinations:
--

1.8.0.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/