Lines Matching refs:call_rcu
149 c. synchronize_rcu() / call_rcu()
155 express synchronize_rcu() in terms of the call_rcu() callback API.
221 The call_rcu() API is an asynchronous callback form of
229 However, the call_rcu() API should not be used lightly, as use
234 of denial-of-service attacks. Code using call_rcu() should limit
365 synchronize_rcu() & call_rcu()
369 rcu_read_unlock(), synchronize_rcu(), and call_rcu() invocations in
371 to their callers and (2) call_rcu() callbacks may be invoked. Efficient
380 synchronize_rcu() and call_rcu() primitives used are the same for all three
514 In such cases, one uses call_rcu() rather than synchronize_rcu().
515 The call_rcu() API is as follows::
517 void call_rcu(struct rcu_head *head, rcu_callback_t func);
542 * Uses call_rcu() to ensure that any readers that might have
558 call_rcu(&old_fp->rcu, foo_reclaim);
576 The use of call_rcu() permits the caller of foo_update_a() to
583 that we are now using call_rcu() rather than synchronize_rcu():
585 - Use call_rcu() **after** removing a data element from an
591 If the callback for call_rcu() is not doing anything more than calling
592 kfree() on the structure, you can use kfree_rcu() instead of call_rcu()
895 mechanism that never blocks, namely call_rcu() or kfree_rcu(), that can
966 using call_rcu() only after all those pointers have been changed.
1042 rcu_read_lock_held call_rcu
1050 rcu_read_lock_bh call_rcu rcu_barrier
1063 rcu_read_lock_sched call_rcu rcu_barrier