Lines Matching refs:synchronize_rcu

121 c.	synchronize_rcu() / call_rcu()
127 express synchronize_rcu() in terms of the call_rcu() callback API.
155 synchronize_rcu()
157 	void synchronize_rcu(void);
162 	Note that synchronize_rcu() will -not- necessarily wait for
169 	 2.                    enters synchronize_rcu()
172 	 5.                     exits synchronize_rcu()
175 	To reiterate, synchronize_rcu() waits only for ongoing RCU
177 	any that begin after synchronize_rcu() is invoked.
179 	Of course, synchronize_rcu() does not necessarily return
184 	further delay synchronize_rcu().
186 	Since synchronize_rcu() is the API that must figure out when
189 	synchronize_rcu()'s overhead must also be quite small.
191 	The call_rcu() API is a callback form of synchronize_rcu(),
200 	of the synchronize_rcu() API generally results in simpler code.
201 	In addition, the synchronize_rcu() API has the nice property
308 	      synchronize_rcu() & call_rcu()
312 rcu_read_unlock(), synchronize_rcu(), and call_rcu() invocations in
313 order to determine when (1) synchronize_rcu() invocations may return
326 a.	synchronize_rcu()	rcu_read_lock() / rcu_read_unlock()
376 	 * Uses synchronize_rcu() to ensure that any readers that might
392 		synchronize_rcu();
431 o	Use synchronize_rcu() -after- removing a data element from an
448 In such cases, one uses call_rcu() rather than synchronize_rcu().
518 that we are now using call_rcu() rather than synchronize_rcu():
579 	void synchronize_rcu(void)
602 and release a global reader-writer lock.  The synchronize_rcu()
604 it.  This means that once synchronize_rcu() exits, all RCU read-side
605 critical sections that were in progress before synchronize_rcu() was
607 synchronize_rcu() would have been able to write-acquire the lock
613 that the only thing that can block rcu_read_lock() is a synchronize_rcu().
614 But synchronize_rcu() does not acquire any locks while holding rcu_gp_mutex,
634 	void synchronize_rcu(void)
648 The implementation of synchronize_rcu() simply schedules itself on each
664 synchronize_rcu().  Once synchronize_rcu() returns, we are guaranteed
714 	+			synchronize_rcu();
762                                        10       synchronize_rcu();
773 a reader-writer lock to a simple spinlock, and a synchronize_rcu()
782 Also, the presence of synchronize_rcu() means that the RCU version of
785 be used in place of synchronize_rcu().
839 	rcu_read_unlock		synchronize_rcu
943 		2.	CPU 1 enters synchronize_rcu(), write-acquiring
963 		readers through synchronize_rcu().  To see this,
974 		cannot be blocked by tasks executing synchronize_rcu().