diff options
| -rw-r--r-- | Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.html b/Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.html index a346ce0116eb..e4d94fba6c89 100644 --- a/Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.html +++ b/Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.html | |||
| @@ -77,7 +77,7 @@ The key point is that the lock-acquisition functions, including | |||
| 77 | <tt>smp_mb__after_unlock_lock()</tt> immediately after successful | 77 | <tt>smp_mb__after_unlock_lock()</tt> immediately after successful |
| 78 | acquisition of the lock. | 78 | acquisition of the lock. |
| 79 | 79 | ||
| 80 | <p>Therefore, for any given <tt>rcu_node</tt> struction, any access | 80 | <p>Therefore, for any given <tt>rcu_node</tt> structure, any access |
| 81 | happening before one of the above lock-release functions will be seen | 81 | happening before one of the above lock-release functions will be seen |
| 82 | by all CPUs as happening before any access happening after a later | 82 | by all CPUs as happening before any access happening after a later |
| 83 | one of the above lock-acquisition functions. | 83 | one of the above lock-acquisition functions. |