Lines Matching refs:call_rcu

121 c.	synchronize_rcu() / call_rcu()
127 express synchronize_rcu() in terms of the call_rcu() callback API.
191 	The call_rcu() API is a callback form of synchronize_rcu(),
199 	However, the call_rcu() API should not be used lightly, as use
204 	of denial-of-service attacks.  Code using call_rcu() should limit
310 	      synchronize_rcu() & call_rcu()
314 rcu_read_unlock(), synchronize_rcu(), and call_rcu() invocations in
316 to their callers and (2) call_rcu() callbacks may be invoked.  Efficient
329 	call_rcu()		rcu_dereference()
450 In such cases, one uses call_rcu() rather than synchronize_rcu().
451 The call_rcu() API is as follows:
453 	void call_rcu(struct rcu_head * head,
479 	 * Uses call_rcu() to ensure that any readers that might have
495 		call_rcu(&old_fp->rcu, foo_reclaim);
513 The use of call_rcu() permits the caller of foo_update_a() to
520 that we are now using call_rcu() rather than synchronize_rcu():
522 o	Use call_rcu() -after- removing a data element from an
528 If the callback for call_rcu() is not doing anything more than calling
529 kfree() on the structure, you can use kfree_rcu() instead of call_rcu()
786 mechanism that never blocks, namely call_rcu() or kfree_rcu(), that can
843 	rcu_read_lock_held	call_rcu