leandrof/linux
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
d8936c0b7e
linux/Documentation/RCU/Design/Requirements
History
Paul E. McKenney d8936c0b7e documentation: Explain why rcu_read_lock() needs no barrier() 
This commit adds a Quick Quiz whose answer explains why the compiler
code reordering enabled by CONFIG_PREEMPT=n's empty rcu_read_lock()
and rcu_read_unlock() functions does not hinder RCU's ability to figure
out which RCU read-side critical sections have completed and not.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
2016-03-31 13:33:20 -07:00
..
2013-08-is-it-dead.png documentation: Record RCU requirements 2015-12-05 12:19:07 -08:00
GPpartitionReaders1.svg documentation: Record RCU requirements 2015-12-05 12:19:07 -08:00
RCUApplicability.svg documentation: Record RCU requirements 2015-12-05 12:19:07 -08:00
ReadersPartitionGP1.svg documentation: Record RCU requirements 2015-12-05 12:19:07 -08:00
Requirements.html documentation: Explain why rcu_read_lock() needs no barrier() 2016-03-31 13:33:20 -07:00
Requirements.htmlx documentation: Explain why rcu_read_lock() needs no barrier() 2016-03-31 13:33:20 -07:00