Searched refs:synchronize_rcu (Results 1 – 25 of 299) sorted by relevance
12345678910>>...12
| /Linux-v5.15/Documentation/RCU/ |
| D | whatisRCU.rst | 140 c. synchronize_rcu() / call_rcu()
146 express synchronize_rcu() in terms of the call_rcu() callback API.
174 synchronize_rcu()
176 void synchronize_rcu(void);
181 Note that synchronize_rcu() will **not** necessarily wait for
188 2. enters synchronize_rcu()
191 5. exits synchronize_rcu()
194 To reiterate, synchronize_rcu() waits only for ongoing RCU
196 any that begin after synchronize_rcu() is invoked.
198 Of course, synchronize_rcu() does not necessarily return
[all …]
|
| D | NMI-RCU.rst | 87 One way to accomplish this is via synchronize_rcu(), perhaps as
91 synchronize_rcu();
94 This works because (as of v4.20) synchronize_rcu() blocks until all
97 Since NMI handlers disable preemption, synchronize_rcu() is guaranteed
99 to free up the handler's data as soon as synchronize_rcu() returns.
|
| D | UP.rst | 52 Why is it *not* legal to invoke synchronize_rcu() in this case?
96 Note that it *is* safe for synchronize_rcu() to return immediately on
100 Why can't synchronize_rcu() return immediately on UP systems running
106 Why is it *not* legal to invoke synchronize_rcu() in this case?
136 Why can't synchronize_rcu() return immediately on UP systems
140 of an RCU read-side critical section. If synchronize_rcu()
|
| D | checklist.rst | 190 6. Since synchronize_rcu() can block, it cannot be called
216 If the updater uses call_rcu() or synchronize_rcu(), then
247 disables BH when updaters use call_rcu() or synchronize_rcu().
249 8. Although synchronize_rcu() is slower than is call_rcu(), it
252 synchronize_rcu() is visible from userspace, synchronize_rcu()
255 synchronize_rcu() without synchronize_rcu()'s multi-millisecond
259 An especially important property of the synchronize_rcu()
261 are delayed for whatever reason, then the synchronize_rcu()
300 d. Periodically invoke synchronize_rcu(), permitting a limited
411 14. The whole point of call_rcu(), synchronize_rcu(), and friends
[all …]
|
| D | rcubarrier.rst | 24 presence? There is a synchronize_rcu() primitive that blocks until all
30 synchronize_rcu();
64 We could try placing a synchronize_rcu() in the module-exit code path,
65 but this is not sufficient. Although synchronize_rcu() does wait for a
68 One might be tempted to try several back-to-back synchronize_rcu()
81 synchronize_rcu(), in particular, if there are no RCU callbacks queued
|
| /Linux-v5.15/include/linux/ |
| D | rcutiny.h | 30 synchronize_rcu(); in synchronize_rcu_expedited()
50 synchronize_rcu(); in kvfree_call_rcu()
|
| D | rcupdate.h | 43 void synchronize_rcu(void);
167 # define synchronize_rcu_tasks synchronize_rcu
201 #define synchronize_rcu_tasks synchronize_rcu
|
| /Linux-v5.15/kernel/rcu/ |
| D | tiny.c | 149 void synchronize_rcu(void) in synchronize_rcu() function
156 EXPORT_SYMBOL_GPL(synchronize_rcu);
|
| /Linux-v5.15/net/hsr/ |
| D | hsr_slave.c | 190 synchronize_rcu(); in hsr_add_port()
220 synchronize_rcu(); in hsr_del_port()
|
| /Linux-v5.15/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 101 14 synchronize_rcu();
105 Because the synchronize_rcu() on line 14 waits for all pre-existing
110 started after the synchronize_rcu() started, and must therefore also
124 | block synchronize_rcu()!!! |
131 | Second, even when using synchronize_rcu(), the other update-side |
165 24 synchronize_rcu();
169 28 synchronize_rcu();
174 the synchronize_rcu() in start_recovery() to guarantee that
181 | Why is the synchronize_rcu() on line 28 needed? |
191 critical section must not contain calls to synchronize_rcu().
[all …]
|
| /Linux-v5.15/net/netfilter/ |
| D | nf_nat_tftp.c | 44 synchronize_rcu(); in nf_nat_tftp_fini()
|
| D | nf_nat_amanda.c | 80 synchronize_rcu(); in nf_nat_amanda_fini()
|
| /Linux-v5.15/net/netfilter/ipvs/ |
| D | ip_vs_fo.c | 69 synchronize_rcu(); in ip_vs_fo_cleanup()
|
| D | ip_vs_lc.c | 83 synchronize_rcu(); in ip_vs_lc_cleanup()
|
| D | ip_vs_ovf.c | 76 synchronize_rcu(); in ip_vs_ovf_cleanup()
|
| D | ip_vs_nq.c | 133 synchronize_rcu(); in ip_vs_nq_cleanup()
|
| D | ip_vs_sed.c | 134 synchronize_rcu(); in ip_vs_sed_cleanup()
|
| D | ip_vs_wlc.c | 106 synchronize_rcu(); in ip_vs_wlc_cleanup()
|
| /Linux-v5.15/kernel/sched/ |
| D | membarrier.c | 453 synchronize_rcu(); in sync_runqueues_membarrier_state()
608 synchronize_rcu(); in SYSCALL_DEFINE3()
|
| /Linux-v5.15/net/caif/ |
| D | cfcnfg.c | 109 synchronize_rcu(); in cfcnfg_create()
121 synchronize_rcu(); in cfcnfg_remove()
197 synchronize_rcu(); in caif_disconnect_client()
583 synchronize_rcu(); in cfcnfg_del_phy_layer()
|
| /Linux-v5.15/Documentation/litmus-tests/rcu/ |
| D | RCU+sync+read.litmus | 33 synchronize_rcu();
|
| /Linux-v5.15/net/ieee802154/ |
| D | core.c | 182 synchronize_rcu(); in wpan_phy_unregister()
306 synchronize_rcu(); in cfg802154_netdev_notifier_call()
|
| /Linux-v5.15/drivers/misc/cxl/ |
| D | base.c | 94 synchronize_rcu(); in unregister_cxl_calls()
|
| /Linux-v5.15/drivers/crypto/nx/ |
| D | nx-common-pseries.c | 812 synchronize_rcu(); in nx842_OF_upd()
823 synchronize_rcu(); in nx842_OF_upd()
1064 synchronize_rcu(); in nx842_probe()
1129 synchronize_rcu(); in nx842_remove()
1260 synchronize_rcu(); in nx842_pseries_exit()
|
| /Linux-v5.15/net/802/ |
| D | stp.c | 93 synchronize_rcu(); in stp_proto_unregister()
|
12345678910>>...12
