Lines Matching refs:call_rcu

126 c.	synchronize_rcu() / call_rcu()
132 express synchronize_rcu() in terms of the call_rcu() callback API.
196 	The call_rcu() API is a callback form of synchronize_rcu(),
204 	However, the call_rcu() API should not be used lightly, as use
209 	of denial-of-service attacks.  Code using call_rcu() should limit
328 	      synchronize_rcu() & call_rcu()
332 rcu_read_unlock(), synchronize_rcu(), and call_rcu() invocations in
334 to their callers and (2) call_rcu() callbacks may be invoked.  Efficient
340 sychronize_rcu() and call_rcu() primitives used are the same for all three
467 In such cases, one uses call_rcu() rather than synchronize_rcu().
468 The call_rcu() API is as follows:
470 	void call_rcu(struct rcu_head * head,
496 	 * Uses call_rcu() to ensure that any readers that might have
512 		call_rcu(&old_fp->rcu, foo_reclaim);
530 The use of call_rcu() permits the caller of foo_update_a() to
537 that we are now using call_rcu() rather than synchronize_rcu():
539 o	Use call_rcu() -after- removing a data element from an
545 If the callback for call_rcu() is not doing anything more than calling
546 kfree() on the structure, you can use kfree_rcu() instead of call_rcu()
817 mechanism that never blocks, namely call_rcu() or kfree_rcu(), that can
876 	rcu_read_lock_held	call_rcu
882 	rcu_read_lock_bh	call_rcu		rcu_barrier
893 	rcu_read_lock_sched	call_rcu		rcu_barrier