| /Linux-v4.19/Documentation/RCU/ |
| D | stallwarn.txt | 38 o Anything that prevents RCU's grace-period kthreads from running.
49 in which case the next RCU grace period can never complete, which
58 RCU grace periods from ever completing. Either way, the
92 that RCU only detects CPU stalls when there is a grace period in progress.
93 No grace period, no CPU stall warnings.
111 CPU stall detector, which detects conditions that unduly delay RCU grace
120 that RCU will wait from the beginning of a grace period until it
164 task stalling the current RCU-tasks grace period.
187 the RCU core for the past three grace periods. In contrast, CPU 16's "(0
189 interrupts during the current stalled grace period.
[all …]
|
| D | rcu.txt | 7 A "grace period" must elapse between the two parts, and this grace period
11 a grace period to elapse, then free the element. See the listRCU.txt
27 o How can the updater tell when a grace period has completed
44 critical sections. These variants of RCU detect grace periods
48 thing at a time, why should I wait for a grace period?
|
| D | rcubarrier.txt | 62 grace period to elapse, it does not wait for the callbacks to complete.
74 a grace period to elapse, rcu_barrier() waits for all outstanding RCU
78 without waiting for a grace period to elapse.
263 are delayed for a full grace period? Couldn't this result in
299 are delayed for a full grace period? Couldn't this result in
307 a grace period from completing on non-CONFIG_PREEMPT kernels,
309 state) before the grace period can complete. However, this is
315 switching, again preventing grace periods from completing. This
|
| D | checklist.txt | 57 to prevent grace periods from ending prematurely, which
203 boot parameter to completely disable expedited grace periods,
248 primitive is that it automatically self-limits: if grace periods
252 cases where grace periods are delayed, as failing to do so can
260 those waiting for a grace period to elapse. Enforce a
268 spinning on the lock could prevent the grace period
273 RCU grace period. There are of course many other
289 advantage of call_rcu_bh()'s faster grace periods. (This
293 number of updates per grace period.
400 Second, grace-period-detection overhead is amortized only
[all …]
|
| D | UP.txt | 21 after a grace period.
43 RCU usage, since call_rcu() must wait for a grace period to elapse.
86 infrastructure -must- respect grace periods, and -must- invoke callbacks
134 end of the grace period, which would come as a nasty shock to
|
| D | torture.txt | 21 bursts help force races between forcing a given grace
22 period and that grace period ending on its own.
30 gp_normal Make the fake writers use normal synchronous grace-period
33 gp_exp Make the fake writers use expedited synchronous grace-period
255 incremented once per grace period subsequently -- and is freed
256 after passing through (RCU_TORTURE_PIPE_LEN-2) grace periods.
264 than in terms of grace periods. The legal number of non-zero
274 passes through a grace period. The last entry should be zero,
|
| D | rculist_nulls.txt | 23 * reuse these object before the RCU grace period, we
100 very very fast (before the end of RCU grace period)
|
| D | rcuref.txt | 109 until after a grace period has elapsed following removal. This means that
|
| D | RTFP.txt | 129 not necessarily exactly the same as, an RCU grace period. In classic
132 the corresponding CPU during the prior grace period. Of course, RCU
206 but if in the same direction, the updater needs to wait for a grace
421 Use fixed time delay to approximate grace period. Very simple,
955 for a grace period before freeing them.
1262 Esben Neilsen suggests read-side suppression of grace-period
1264 is indefinite grace periods... But this is OK for experimentation
1618 SRCU's grace periods are too slow for Jens, even after a
2173 RCU with combining-tree-based grace-period detection,
2256 ,Title="[{PATCH} -tip 0/3] expedited 'big hammer' {RCU} grace periods"
[all …]
|
| D | whatisRCU.txt | 207 of automatically limiting update rate should grace periods
378 * frees up the old structure after a grace period.
451 In the example above, foo_update_a() blocks until a grace period elapses.
461 This function invokes func(head) after a grace period has elapsed.
479 * frees up the old structure after a grace period.
934 d. Do you need RCU grace periods to complete even in the face
1038 grace periods short if need be (for example, if running
|
| D | arrayRCU.txt | 103 to free the array after a grace period has elapsed.
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | quota.txt | 11 softlimit but only for limited period of time. This period is called "grace
12 period" or "grace time". When grace time is over, user is not able to allocate
15 Quota limits (and amount of grace time) are set independently for each
23 When user exceeds a softlimit, runs out of grace time or reaches hardlimit,
53 than given grace period
57 longer than given grace period.
|
| D | path-lookup.txt | 102 list. The object will not be reused until an RCU grace period is complete.
109 high to wait for a grace period after removing the dentry and before inserting
114 new list before waiting for a grace period, this can result in a concurrent RCU
161 Because we didn't wait for a grace period, there may be a concurrent lookup
|
| /Linux-v4.19/kernel/rcu/ |
| D | Kconfig | 155 number of cache misses incurred during RCU's grace-period
174 bool "Accelerate last non-dyntick-idle CPU's grace periods"
183 hand, this option increases the duration of RCU grace periods,
187 don't care about increased grace-period durations.
197 block the current preemptible RCU grace period for too long.
205 int "Milliseconds to delay boosting after RCU grace-period start"
211 a given grace period before priority-boosting preempted RCU
212 readers blocking that grace period. Note that any RCU reader
213 blocking an expedited RCU grace period is boosted immediately.
|
| D | Kconfig.debug | 54 If a given RCU grace period extends more than the specified
56 RCU grace period persists, additional CPU stall warnings are
|
| /Linux-v4.19/fs/nfs_common/ |
| D | Makefile | 8 obj-$(CONFIG_GRACE_PERIOD) += grace.o
|
| /Linux-v4.19/tools/testing/selftests/rcutorture/bin/ |
| D | kvm.sh | 173 --shutdown-grace)
174 checkarg --shutdown-grace "(seconds)" "$#" "$2" '^[0-9]*$' '^error'
|
| /Linux-v4.19/drivers/firewire/ |
| D | core-card.c | 306 int gap_count, generation, grace, rcode; in bm_work() local
342 grace = time_after64(get_jiffies_64(), in bm_work()
347 (card->bm_generation != generation && grace)) { in bm_work()
|
| /Linux-v4.19/tools/memory-model/Documentation/ |
| D | explanation.txt | 881 grace periods obey the rules of RCU, in particular, the
1458 rests on two concepts: grace periods and read-side critical sections.
1460 A grace period is the span of time occupied by a call to
1468 span a full grace period. In more detail, the Guarantee says:
1470 If a critical section starts before a grace period then it
1471 must end before the grace period does. In addition, every
1474 the end of the grace period.
1476 If a critical section ends after a grace period ends then it
1477 must start after the grace period does. In addition, every
1478 store that propagates to the grace period's CPU before the
[all …]
|
| /Linux-v4.19/Documentation/filesystems/nfs/ |
| D | nfsd-admin-interfaces.txt | 24 On startup, nfsd and lockd grace periods start.
|
| /Linux-v4.19/fs/lockd/ |
| D | svc.c | 98 static void grace_ender(struct work_struct *grace) in grace_ender() argument
100 struct delayed_work *dwork = to_delayed_work(grace); in grace_ender()
|
| /Linux-v4.19/Documentation/core-api/ |
| D | assoc_array.rst | 82 after an RCU grace period has passed - thus allowing access functions to
160 Free the specified object. Note that this may be called an RCU grace period
510 until after the RCU grace period.
514 after the RCU grace period.
552 Obsolete blocks and leaves are freed up after an RCU grace period has passed,
|
| /Linux-v4.19/tools/memory-model/ |
| D | linux-kernel.cat | 106 * Any sequence containing at least as many grace periods as RCU read-side
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | kernel-parameters.txt | 2161 lockd.nlm_grace_period=P [NFS] Assign grace period.
3574 RCU grace-period cleanup.
3578 RCU grace-period initialization.
3582 RCU grace-period pre-initialization, that is,
3602 given grace period before RCU starts
3607 Set delay from grace-period initialization to
3621 and for the RCU grace-period kthreads (rcu_bh,
3632 on the per-CPU grace-period kthreads, but increases
3654 Cause the grace-period kthread to get an extra
3662 grace-period primitives such as call_rcu().
[all …]
|
| /Linux-v4.19/Documentation/ |
| D | kref.txt | 316 rcu grace period after release_entry_rcu was called. That can be accomplished
|
