Lines Matching refs:rcu_barrier

75 rcu_barrier()
78 We instead need the rcu_barrier() primitive.  Rather than waiting for
79 a grace period to elapse, rcu_barrier() waits for all outstanding RCU
80 callbacks to complete.  Please note that rcu_barrier() does **not** imply
82 anywhere, rcu_barrier() is within its rights to return immediately,
85 Pseudo-code using rcu_barrier() is as follows:
88    2. Execute rcu_barrier().
92 must match the flavor of rcu_barrier() with that of call_rcu().  If your
94 flavors of rcu_barrier() when unloading that module.  For example, if
99  1 rcu_barrier();
103 The rcutorture module makes use of rcu_barrier() in its exit function
158  53   rcu_barrier();
178 RCU callbacks will be posted. The rcu_barrier() call on line 53 waits
187 	Is there any other situation where rcu_barrier() might  argument
194 the timers, and only then invoke rcu_barrier() to wait for any remaining
198 rcu_barrier() before unloading.  Similarly, if your module uses
201 **and** call_srcu(), then you will need to invoke rcu_barrier() **and**
205 Implementing rcu_barrier()
208 Dipankar Sarma's implementation of rcu_barrier() makes use of the fact
214 The original code for rcu_barrier() was as follows::
216  1  void rcu_barrier(void)
229 use rcu_barrier_mutex to ensure that only one rcu_barrier() is using the
277 	rcu_barrier() returning prematurely?
281 The current rcu_barrier() implementation is more complex, due to the need
287 rcu_barrier() Summary
290 The rcu_barrier() primitive has seen relatively little use, since most
292 you are using RCU from an unloadable module, you need to use rcu_barrier()
302 	Is there any other situation where rcu_barrier() might
305 Answer: Interestingly enough, rcu_barrier() was not originally
308 	filesystem-unmount time. Dipankar Sarma coded up rcu_barrier()
313 	implementing rcutorture, and found that rcu_barrier() solves
325 	rcu_barrier() returning prematurely?
349 	is to add an rcu_read_lock() before line 8 of rcu_barrier()