kernel/rcu/srcutree.c

472 	 * synchronize_srcu() in the write side. In this case smp_mb()s
476 	 * after the synchronize_srcu() from being executed before the
566  * We use an adaptive strategy for synchronize_srcu() and especially for
1375  * Helper function for synchronize_srcu() and synchronize_srcu_expedited().
1387 			 "Illegal synchronize_srcu() in same-type SRCU (or in RCU) read-side critical section");
1417  * memory-ordering properties as does synchronize_srcu().
1426  * synchronize_srcu - wait for prior SRCU read-side critical-section completion
1430  * possible starvation of synchronize_srcu(), it waits for the count of
1436  * Note that it is illegal to call synchronize_srcu() from the corresponding
1438  * However, it is perfectly legal to call synchronize_srcu() on one
1442  * There are memory-ordering constraints implied by synchronize_srcu().
1443  * On systems with more than one CPU, when synchronize_srcu() returns,
1446  * whose beginning preceded the call to synchronize_srcu().  In addition,
1448  * the return from synchronize_srcu() is guaranteed to have executed a
1449  * full memory barrier after the beginning of synchronize_srcu() and before
1454  * Furthermore, if CPU A invoked synchronize_srcu(), which returned
1457  * synchronize_srcu().  This guarantee applies even if CPU A and CPU B
1461  * synchronize_srcu(), srcu_read_lock(), and srcu_read_unlock() are
1472 void synchronize_srcu(struct srcu_struct *ssp)
1479 EXPORT_SYMBOL_GPL(synchronize_srcu);