Lines Matching refs:invocation

193 that waits, directly or indirectly, on completion of an invocation of
507    CPUs during that invocation, then each of the CPUs in that group is
1222 of synchronize_rcu(), thus amortizing the per-invocation overhead
1357 | be correct, given that the invocation of the callback and the freeing |
1414 In theory, delaying grace-period completion and callback invocation is
1432 to ensure timely completion of grace periods and timely invocation of
1465 invocation of callbacks when any given non-\ ``rcu_nocbs`` CPU has
1477    invocation at the expense of degrading realtime response.
1482 RCU`_. Even for RCU, callback-invocation forward
1486 both ``rcu_nocbs`` CPUs and high call_rcu() invocation rates, then
1757 This delay in callback invocation is due to the fact that RCU does not
1873 invocation of call_rcu(), then invoke rcu_barrier(). In theory,
2018 reorder a get_user() invocation into an RCU read-side critical section.
2253 invocations can safely be deferred. Deferring invocation could
2402 invocation will be delayed until the time of the
2546 by default), and if a synchronize_srcu() invocation ends this idle
2547 period, that invocation will be automatically expedited.
2724 invocation.