Lines Matching refs:call_rcu

140 c.	synchronize_rcu() / call_rcu()
146 express synchronize_rcu() in terms of the call_rcu() callback API.
210 	The call_rcu() API is a callback form of synchronize_rcu(),
218 	However, the call_rcu() API should not be used lightly, as use
223 	of denial-of-service attacks.  Code using call_rcu() should limit
351 	      synchronize_rcu() & call_rcu()
355 rcu_read_unlock(), synchronize_rcu(), and call_rcu() invocations in
357 to their callers and (2) call_rcu() callbacks may be invoked.  Efficient
363 synchronize_rcu() and call_rcu() primitives used are the same for all three
497 In such cases, one uses call_rcu() rather than synchronize_rcu().
498 The call_rcu() API is as follows::
500 	void call_rcu(struct rcu_head * head,
526 	 * Uses call_rcu() to ensure that any readers that might have
542 		call_rcu(&old_fp->rcu, foo_reclaim);
560 The use of call_rcu() permits the caller of foo_update_a() to
567 that we are now using call_rcu() rather than synchronize_rcu():
569 -	Use call_rcu() **after** removing a data element from an
575 If the callback for call_rcu() is not doing anything more than calling
576 kfree() on the structure, you can use kfree_rcu() instead of call_rcu()
871 mechanism that never blocks, namely call_rcu() or kfree_rcu(), that can
939 	rcu_read_lock_held	call_rcu
947 	rcu_read_lock_bh	call_rcu		rcu_barrier
960 	rcu_read_lock_sched	call_rcu		rcu_barrier