Lines Matching refs:callbacks

59 If we unload the module while some RCU callbacks are pending,
60 the CPUs executing these callbacks are going to be severely
66 grace period to elapse, it does not wait for the callbacks to complete.
70 heavy RCU-callback load, then some of the callbacks might be deferred
80 callbacks to complete.  Please note that rcu_barrier() does **not** imply
81 synchronize_rcu(), in particular, if there are no RCU callbacks queued
87    1. Prevent any new RCU callbacks from being posted.
157  52   /* Wait for all RCU callbacks to fire. */
170 Line 6 sets a global variable that prevents any RCU callbacks from
172 RCU callbacks rarely include calls to call_rcu(). However, the rcutorture
178 RCU callbacks will be posted. The rcu_barrier() call on line 53 waits
179 for any pre-existing callbacks to complete.
195 RCU callbacks to complete.
209 that RCU callbacks are never reordered once queued on one of the per-CPU
212 which point, all earlier RCU callbacks are guaranteed to have completed.
346 	queue for RCU callbacks, and thus do not suffer from this