| /linux-4.4.14/Documentation/RCU/ |
| D | trace.txt | 45 Displays statistics for expedited grace periods.
47 Displays grace-period counters.
78 o "c" is the count of grace periods that this CPU believes have
81 which has been offline through 16 RCU grace periods. It is not
82 unusual to see offline CPUs lagging by thousands of grace periods.
83 Note that although the grace-period number is an unsigned long,
87 o "g" is the count of grace periods that this CPU believes have
90 has already reported a quiescent state for the last RCU grace
95 for the current grace period. It is possible for "pq" to be
99 yet reported for this grace period, or (3) both.
[all …]
|
| D | stallwarn.txt | 4 detector, which detects conditions that unduly delay RCU grace periods.
13 that RCU will wait from the beginning of a grace period until it
57 task stalling the current RCU-tasks grace period.
86 Finally, if the grace period ends just as the stall warning starts
93 on how the stall warning and the grace-period initialization happen to
112 grace period. If the CPU was not yet aware of the current grace
114 indicates how many grace periods behind the CPU is.
127 last noted the beginning of a grace period, which might be the current
128 (stalled) grace period, or it might be some earlier grace period (for
147 If the relevant grace-period kthread has been unable to run prior to
[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
294 are delayed for a full grace period? Couldn't this result in
302 a grace period from completing on non-CONFIG_PREEMPT kernels,
304 state) before the grace period can complete. However, this is
310 switching, again preventing grace periods from completing. This
|
| 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 | 36 bursts help force races between forcing a given grace
37 period and that grace period ending on its own.
45 gp_normal Make the fake writers use normal synchronous grace-period
48 gp_exp Make the fake writers use expedited synchronous grace-period
270 incremented once per grace period subsequently -- and is freed
271 after passing through (RCU_TORTURE_PIPE_LEN-2) grace periods.
279 than in terms of grace periods. The legal number of non-zero
289 passes through a grace period. The last entry should be zero,
|
| D | checklist.txt | 47 to prevent grace periods from ending prematurely, which
234 primitive is that it automatically self-limits: if grace periods
238 cases where grace periods are delayed, as failing to do so can
246 those waiting for a grace period to elapse. Enforce a
254 spinning on the lock could prevent the grace period
259 RCU grace period. There are of course many other
275 advantage of call_rcu_bh()'s faster grace periods. (This
279 number of updates per grace period.
387 Second, grace-period-detection overhead is amortized only
428 grace period has elapsed since the last time that you
|
| 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 | 202 of automatically limiting update rate should grace periods
373 * frees up the old structure after a grace period.
446 In the example above, foo_update_a() blocks until a grace period elapses.
456 This function invokes func(head) after a grace period has elapsed.
474 * frees up the old structure after a grace period.
910 d. Do you need RCU grace periods to complete even in the face
1013 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-4.4.14/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-4.4.14/fs/nfs_common/ |
| D | Makefile | 8 obj-$(CONFIG_GRACE_PERIOD) += grace.o
|
| /linux-4.4.14/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-4.4.14/Documentation/filesystems/nfs/ |
| D | nfsd-admin-interfaces.txt | 24 On startup, nfsd and lockd grace periods start.
|
| /linux-4.4.14/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run.sh | 41 grace=120
|
| /linux-4.4.14/fs/lockd/ |
| D | svc.c | 91 static void grace_ender(struct work_struct *grace) in grace_ender() argument
93 struct delayed_work *dwork = container_of(grace, struct delayed_work, in grace_ender()
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 1275 bool "Slow down RCU grace-period pre-initialization to expose races"
1278 This option delays grace-period pre-initialization (the
1282 involving grace-period pre-initialization, in other words, it
1284 grace-period latency, especially on systems with large numbers
1292 int "How much to slow down RCU grace-period pre-initialization"
1301 bool "Slow down RCU grace-period initialization to expose races"
1304 This option delays grace-period initialization for a few
1307 grace-period initialization, in other words, it makes your
1308 kernel less stable. It can also greatly increase grace-period
1317 int "How much to slow down RCU grace-period initialization"
[all …]
|
| /linux-4.4.14/drivers/staging/lustre/lustre/include/ |
| D | lustre_sec.h | 371 int grace);
579 int grace,
|
| /linux-4.4.14/Documentation/ |
| D | assoc_array.txt | 99 after an RCU grace period has passed - thus allowing access functions to
177 Free the specified object. Note that this may be called an RCU grace
530 until after the RCU grace period.
534 after the RCU grace period.
572 Obsolete blocks and leaves are freed up after an RCU grace period has passed,
|
| D | kref.txt | 297 rcu grace period after release_entry_rcu was called. That can be accomplished
|
| D | kernel-parameters.txt | 1878 lockd.nlm_grace_period=P [NFS] Assign grace period.
3093 RCU grace-period cleanup. This only has effect
3098 RCU grace-period initialization. This only has
3104 RCU grace-period pre-initialization, that is,
3125 given grace period before RCU starts
3130 Set delay from grace-period initialization to
3144 and for the RCU grace-period kthreads (rcu_bh,
3155 on the per-CPU grace-period kthreads, but increases
3300 Use expedited grace-period primitives, for
|
| /linux-4.4.14/drivers/staging/lustre/lustre/ptlrpc/ |
| D | sec_null.c | 150 int grace, int force) in null_flush_ctx_cache() argument
|
| D | sec.c | 1166 int grace, int force) in sec_cop_flush_ctx_cache() argument
1173 return policy->sp_cops->flush_ctx_cache(sec, uid, grace, force); in sec_cop_flush_ctx_cache()
1446 uid_t uid, int grace, int force) in import_flush_ctx_common() argument
1457 sec_cop_flush_ctx_cache(sec, uid, grace, force); in import_flush_ctx_common()
|
| D | sec_plain.c | 518 uid_t uid, int grace, int force) in plain_flush_ctx_cache() argument
|
| /linux-4.4.14/init/ |
| D | Kconfig | 603 number of cache misses incurred during RCU's grace-period
616 bool "Accelerate last non-dyntick-idle CPU's grace periods"
625 hand, this option increases the duration of RCU grace periods,
629 don't care about increased grace-period durations.
647 block the current preemptible RCU grace period for too long.
686 int "Milliseconds to delay boosting after RCU grace-period start"
692 a given grace period before priority-boosting preempted RCU
693 readers blocking that grace period. Note that any RCU reader
694 blocking an expedited RCU grace period is boosted immediately.
779 This option enables expedited grace periods at boot time,
|
| /linux-4.4.14/Documentation/security/ |
| D | keys.txt | 1087 to set the pointer and dispose of the old contents after a grace period.
|