Lines Matching refs:rcu_barrier

51 rcu_barrier()
54 This situation can be handled by the rcu_barrier() primitive.  Rather
55 than waiting for a grace period to elapse, rcu_barrier() waits for all
56 outstanding RCU callbacks to complete.  Please note that rcu_barrier()
58 callbacks queued anywhere, rcu_barrier() is within its rights to return
61 Pseudo-code using rcu_barrier() is as follows:
64    2. Execute rcu_barrier().
75   1  rcu_barrier();
82 An ancient version of the rcutorture module makes use of rcu_barrier()
137  53    rcu_barrier();
157 RCU callbacks will be posted. The rcu_barrier() call on line 53 waits
166 	Is there any other situation where rcu_barrier() might
174 timers, and only then invoke rcu_barrier() to wait for any remaining
178 rcu_barrier() before unloading.  Similarly, if your module uses
182 rcu_barrier() **and** srcu_barrier().
185 Implementing rcu_barrier()
188 Dipankar Sarma's implementation of rcu_barrier() makes use of the fact
194 The original code for rcu_barrier() was roughly as follows::
196   1  void rcu_barrier(void)
211 use rcu_barrier_mutex to ensure that only one rcu_barrier() is using the
270 	rcu_barrier() returning prematurely?
274 The current rcu_barrier() implementation is more complex, due to the need
281 rcu_barrier() Summary
284 The rcu_barrier() primitive is used relatively infrequently, since most
286 you are using RCU from an unloadable module, you need to use rcu_barrier()
296 	Is there any other situation where rcu_barrier() might
300 	Interestingly enough, rcu_barrier() was not originally
303 	filesystem-unmount time. Dipankar Sarma coded up rcu_barrier()
308 	implementing rcutorture, and found that rcu_barrier() solves
328 	Note that this was not a problem when the rcu_barrier() code
333 	with the advent of preemptible RCU, rcu_barrier() no longer
354 	rcu_barrier() returning prematurely?