Searched refs:synchronize_rcu (Results 1 – 9 of 9) sorted by relevance
| /tools/include/linux/ |
| D | kernel.h | 126 #define synchronize_rcu() macro
|
| /tools/memory-model/Documentation/ |
| D | cheatsheet.txt | 14 smp_mb() & synchronize_rcu() CP Y Y Y Y Y Y Y Y
|
| D | ordering.txt | 114 primitives include synchronize_rcu(), synchronize_rcu_expedited(),
121 need a synchronize_rcu() to interact with readers, it costs you nothing
382 with synchronize_rcu(), synchronize_rcu_expedited(), and call_rcu().
383 The way this works is that if a given call to synchronize_rcu() cannot
385 that synchronize_rcu() must block until the matching rcu_read_unlock()
386 is reached. For more information, please see the synchronize_rcu()
|
| D | explanation.txt | 780 Strong fences, including smp_mb() and synchronize_rcu(), force
825 rcu_read_lock(), rcu_read_unlock(), and synchronize_rcu() fences have
973 A strong (smp_mb() or synchronize_rcu()) fence occurs between
1437 synchronize_rcu(). A read-side critical section (or just critical
1477 synchronize_rcu();
1484 synchronize_rcu(), so P0's critical section must have started before
1496 some time before the grace period's synchronize_rcu() call returns.
1498 synchronize_rcu() routine will execute an smp_mb() fence at its start
1508 rcu_read_unlock(), or synchronize_rcu()) then among other things,
1524 and that event is a synchronize_rcu() fence (i.e., a grace
[all …]
|
| D | litmus-tests.txt | 850 31 synchronize_rcu(); // Wait one grace period.
1003 process that invokes synchronize_rcu() and the body of the
|
| /tools/memory-model/ |
| D | linux-kernel.bell | 30 'sync-rcu (*synchronize_rcu*) ||
|
| D | linux-kernel.def | 48 synchronize_rcu() { __fence{sync-rcu}; }
|
| D | linux-kernel.cat | 117 * The synchronize_rcu() strong fence is special in that it can order not
|
| /tools/testing/nvdimm/test/ |
| D | iomap.c | 39 synchronize_rcu(); in nfit_test_teardown()
|