diff options
| author |   Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2011-07-31 22:33:02 -0700 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2011-09-28 21:38:34 -0700 |
| commit | 6846c0c54074d47927c90eab4a805115e1ae3292 (patch) | |
| tree | 8f074445ca802a48d976b9a9c8595ac7fe603f22 /kernel/rtmutex.c | |
| parent | rcu: Make rcu_assign_pointer() unconditionally insert a memory barrier (diff) | |
| download | wireguard-linux-6846c0c54074d47927c90eab4a805115e1ae3292.tar.xz wireguard-linux-6846c0c54074d47927c90eab4a805115e1ae3292.zip | |
rcu: Improve rcu_assign_pointer() and RCU_INIT_POINTER() documentation
The differences between rcu_assign_pointer() and RCU_INIT_POINTER() are
subtle, and it is easy to use the the cheaper RCU_INIT_POINTER() when
the more-expensive rcu_assign_pointer() should have been used instead.
The consequences of this mistake are quite severe.
This commit therefore carefully lays out the situations in which it it
permissible to use RCU_INIT_POINTER().
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'kernel/rtmutex.c')
0 files changed, 0 insertions, 0 deletions