mirror of
https://github.com/FEX-Emu/linux.git
synced 2024-12-24 18:38:38 +00:00
documentation: No acquire/release for RCU readers
Documentation/memory-barriers.txt calls out RCU as one of the sets of primitives associated with ACQUIRE and RELEASE. There really is an association in that rcu_assign_pointer() includes a RELEASE operation, but a quick read can convince people that rcu_read_lock() and rcu_read_unlock() have ACQUIRE and RELEASE semantics, which they do not. This commit therefore removes RCU from this list in order to avoid this confusion. Reported-by: Boqun Feng <boqun.feng@gmail.com> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Reviewed-by: Josh Triplett <josh@joshtriplett.org>
This commit is contained in:
parent
19a5ecde08
commit
27566139b6
@ -1789,7 +1789,6 @@ The Linux kernel has a number of locking constructs:
|
|||||||
(*) mutexes
|
(*) mutexes
|
||||||
(*) semaphores
|
(*) semaphores
|
||||||
(*) R/W semaphores
|
(*) R/W semaphores
|
||||||
(*) RCU
|
|
||||||
|
|
||||||
In all cases there are variants on "ACQUIRE" operations and "RELEASE" operations
|
In all cases there are variants on "ACQUIRE" operations and "RELEASE" operations
|
||||||
for each construct. These operations all imply certain barriers:
|
for each construct. These operations all imply certain barriers:
|
||||||
|
Loading…
Reference in New Issue
Block a user