| /Linux-v5.4/Documentation/RCU/ |
| D | stallwarn.txt | 35 o Anything that prevents RCU's grace-period kthreads from running.
46 in which case the next RCU grace period can never complete, which
55 RCU grace periods from ever completing. Either way, the
95 RCU only detects CPU stalls when there is a grace period in progress.
96 No grace period, no CPU stall warnings.
114 CPU stall detector, which detects conditions that unduly delay RCU grace
123 that RCU will wait from the beginning of a grace period until it
167 task stalling the current RCU-tasks grace period.
189 the RCU core for the past three grace periods. In contrast, CPU 16's "(0
191 interrupts during the current stalled grace period.
[all …]
|
| D | rcu.rst | 9 A "grace period" must elapse between the two parts, and this grace period
13 a grace period to elapse, then free the element. See the
30 - How can the updater tell when a grace period has completed
47 critical sections. These variants of RCU detect grace periods
51 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.
262 are delayed for a full grace period? Couldn't this result in
298 are delayed for a full grace period? Couldn't this result in
306 a grace period from completing on non-CONFIG_PREEMPT kernels,
308 state) before the grace period can complete. However, this is
314 switching, again preventing grace periods from completing. This
|
| D | checklist.txt | 57 to prevent grace periods from ending prematurely, which
200 boot parameter to completely disable expedited grace periods,
245 primitive is that it automatically self-limits: if grace periods
249 cases where grace periods are delayed, as failing to do so can
257 those waiting for a grace period to elapse. Enforce a
265 spinning on the lock could prevent the grace period
270 RCU grace period. There are of course many other
286 number of updates per grace period.
372 Second, grace-period-detection overhead is amortized only
422 grace period has elapsed since the last time that you
[all …]
|
| D | UP.rst | 23 after a grace period.
45 RCU usage, since call_rcu() must wait for a grace period to elapse.
93 infrastructure *must* respect grace periods, and *must* invoke callbacks
142 end of the grace period, which would come as a nasty shock to
|
| D | torture.txt | 90 incremented once per grace period subsequently -- and is freed
91 after passing through (RCU_TORTURE_PIPE_LEN-2) grace periods.
99 than in terms of grace periods. The legal number of non-zero
109 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 | 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
390 * frees up the old structure after a grace period.
463 In the example above, foo_update_a() blocks until a grace period elapses.
473 This function invokes func(head) after a grace period has elapsed.
491 * frees up the old structure after a grace period.
948 d. Do you need RCU grace periods to complete even in the face
1053 grace periods short if need be (for example, if running
|
| D | rcuref.txt | 113 until after a grace period has elapsed following removal. This means that
|
| D | arrayRCU.txt | 103 to free the array after a grace period has elapsed.
|
| /Linux-v5.4/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-v5.4/kernel/rcu/ |
| D | Kconfig | 126 number of cache misses incurred during RCU's grace-period
145 bool "Accelerate last non-dyntick-idle CPU's grace periods"
154 hand, this option increases the duration of RCU grace periods,
158 don't care about increased grace-period durations.
168 block the current preemptible RCU grace period for too long.
176 int "Milliseconds to delay boosting after RCU grace-period start"
182 a given grace period before priority-boosting preempted RCU
183 readers blocking that grace period. Note that any RCU reader
184 blocking an expedited RCU grace period is boosted immediately.
|
| D | Kconfig.debug | 66 If a given RCU grace period extends more than the specified
68 RCU grace period persists, additional CPU stall warnings are
|
| /Linux-v5.4/fs/nfs_common/ |
| D | Makefile | 9 obj-$(CONFIG_GRACE_PERIOD) += grace.o
|
| /Linux-v5.4/tools/testing/selftests/rcutorture/bin/ |
| D | kvm.sh | 164 --shutdown-grace)
165 checkarg --shutdown-grace "(seconds)" "$#" "$2" '^[0-9]*$' '^error'
|
| /Linux-v5.4/drivers/firewire/ |
| D | core-card.c | 293 int gap_count, generation, grace, rcode; in bm_work() local
329 grace = time_after64(get_jiffies_64(), in bm_work()
334 (card->bm_generation != generation && grace)) { in bm_work()
|
| /Linux-v5.4/Documentation/filesystems/nfs/ |
| D | nfsd-admin-interfaces.txt | 24 On startup, nfsd and lockd grace periods start.
|
| /Linux-v5.4/tools/memory-model/Documentation/ |
| D | explanation.txt | 877 grace periods obey the rules of RCU, in particular, the
1432 rests on two concepts: grace periods and read-side critical sections.
1434 A grace period is the span of time occupied by a call to
1442 span a full grace period. In more detail, the Guarantee says:
1444 For any critical section C and any grace period G, at least
1456 before and end after a grace period.
1483 P1's grace period, contrary to part (2) of the Guarantee. On the
1486 the grace period, contrary to part (1). Together the results violate
1492 starts before a grace period does then the critical section's CPU will
1494 some time before the grace period's synchronize_rcu() call returns.
[all …]
|
| /Linux-v5.4/fs/lockd/ |
| D | svc.c | 99 static void grace_ender(struct work_struct *grace) in grace_ender() argument
101 struct delayed_work *dwork = to_delayed_work(grace); in grace_ender()
|
| /Linux-v5.4/tools/memory-model/ |
| D | linux-kernel.cat | 124 * Any sequence containing at least as many grace periods as RCU read-side
127 * Likewise for SRCU grace periods and read-side critical sections, provided
|
| /Linux-v5.4/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-v5.4/Documentation/admin-guide/ |
| D | kernel-parameters.txt | 2286 lockd.nlm_grace_period=P [NFS] Assign grace period.
3824 RCU grace-period cleanup.
3828 RCU grace-period initialization.
3832 RCU grace-period pre-initialization, that is,
3857 Set delay from grace-period initialization to
3869 given grace period before RCU starts
3885 and for the RCU grace-period kthreads (rcu_bh,
3896 the wakeup overhead on the global grace-period
3898 each group's NOCB grace-period kthread.
3919 Cause the grace-period kthread to get an extra
[all …]
|
| /Linux-v5.4/Documentation/ |
| D | kref.txt | 316 rcu grace period after release_entry_rcu was called. That can be accomplished
|
