diff options
| author | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2017-06-06 15:04:03 -0700 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2017-08-17 07:29:48 -0700 |
| commit | 4de5f89ef8498e012ba4755b9b63df28c1382690 (patch) | |
| tree | aa454d59a4b6189ed7f6d064aaf9826fbfe6a344 /Documentation/RCU/rcubarrier.txt | |
| parent | f99bcb2cdb5843548a2b0b78157cb7a0b4c7ccac (diff) | |
doc: Update RCU documentation
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'Documentation/RCU/rcubarrier.txt')
| -rw-r--r-- | Documentation/RCU/rcubarrier.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/RCU/rcubarrier.txt b/Documentation/RCU/rcubarrier.txt index b10cfe711e68..5d7759071a3e 100644 --- a/Documentation/RCU/rcubarrier.txt +++ b/Documentation/RCU/rcubarrier.txt @@ -263,6 +263,11 @@ Quick Quiz #2: What happens if CPU 0's rcu_barrier_func() executes are delayed for a full grace period? Couldn't this result in rcu_barrier() returning prematurely? +The current rcu_barrier() implementation is more complex, due to the need +to avoid disturbing idle CPUs (especially on battery-powered systems) +and the need to minimally disturb non-idle CPUs in real-time systems. +However, the code above illustrates the concepts. + rcu_barrier() Summary |