Lines Matching refs:callbacks

55 If we unload the module while some RCU callbacks are pending,
56 the CPUs executing these callbacks are going to be severely
62 grace period to elapse, it does not wait for the callbacks to complete.
66 heavy RCU-callback load, then some of the callbacks might be deferred
75 callbacks to complete.  Please note that rcu_barrier() does -not- imply
76 synchronize_rcu(), in particular, if there are no RCU callbacks queued
82    1. Prevent any new RCU callbacks from being posted.
153 52   /* Wait for all RCU callbacks to fire. */
166 Line 6 sets a global variable that prevents any RCU callbacks from
168 RCU callbacks rarely include calls to call_rcu(). However, the rcutorture
174 RCU callbacks will be posted. The rcu_barrier() call on line 53 waits
175 for any pre-existing callbacks to complete.
186 RCU callbacks to complete.
199 that RCU callbacks are never reordered once queued on one of the per-CPU
202 which point, all earlier RCU callbacks are guaranteed to have completed.
316 	queue for RCU callbacks, and thus do not suffer from this