Lines Matching defs:synchronize_srcu

528 	 * synchronize_srcu() in the write side. In this case smp_mb()s
532 	 * Z) to prevent accesses after the synchronize_srcu() from being
603  * We use an adaptive strategy for synchronize_srcu() and especially for
1456  * Helper function for synchronize_srcu() and synchronize_srcu_expedited().
1468 			 "Illegal synchronize_srcu() in same-type SRCU (or in RCU) read-side critical section");
1498  * memory-ordering properties as does synchronize_srcu().
1507  * synchronize_srcu - wait for prior SRCU read-side critical-section completion
1511  * possible starvation of synchronize_srcu(), it waits for the count of
1518  * Note that it is illegal to call synchronize_srcu() from the corresponding
1520  * However, it is perfectly legal to call synchronize_srcu() on one
1524  * There are memory-ordering constraints implied by synchronize_srcu().
1525  * On systems with more than one CPU, when synchronize_srcu() returns,
1528  * whose beginning preceded the call to synchronize_srcu().  In addition,
1530  * the return from synchronize_srcu() is guaranteed to have executed a
1531  * full memory barrier after the beginning of synchronize_srcu() and before
1536  * Furthermore, if CPU A invoked synchronize_srcu(), which returned
1539  * synchronize_srcu().  This guarantee applies even if CPU A and CPU B
1543  * synchronize_srcu(), srcu_read_lock(), and srcu_read_unlock() are
1555 void synchronize_srcu(struct srcu_struct *ssp)
1562 EXPORT_SYMBOL_GPL(synchronize_srcu);