Lines Matching refs:call_rcu

4 A common misconception is that, on UP systems, the call_rcu() primitive
20 which deletes element B, and then invokes call_rcu() to free element B
23 Now, if call_rcu() were to directly invoke its arguments, then upon return
28 This same problem can occur if call_rcu() is invoked from a hardware
35 by having call_rcu() directly invoke its arguments only if it was called
41 deletes element B from the list, then passes it to call_rcu() for deferred
43 RCU usage, since call_rcu() must wait for a grace period to elapse.
44 Therefore, in this case, allowing call_rcu() to immediately invoke
46 underlying RCU, namely that call_rcu() defers invoking its arguments until
55 Suppose that call_rcu() is invoked while holding a lock, and that the
57 call_rcu() were to directly invoke the callback, the result would
61 the call_rcu() is delayed until after the lock is released.  However,
64 1.	If a number of items need to be passed to call_rcu() within
70 	so that delaying the call_rcu() until the lock is released
76 If call_rcu() directly invokes the callback, painful locking restrictions
84 Permitting call_rcu() to immediately invoke its arguments breaks RCU,