| /linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| A D | Expedited-Grace-Periods.rst | 8 This document describes RCU's expedited grace periods.
23 grace period.
32 state, the expedited grace period has completed.
54 Otherwise, the expedited grace period will use
75 the CPU is no longer blocking the grace period.
251 If each grace-period request was carried out separately, expedited grace
270 grace period.
420 previous grace period's wakeups complete before the next grace period's
436 stalls just as normal grace periods do.
448 | grace period in progress, in which case the normal grace period |
[all …]
|
| /linux/Documentation/RCU/Design/Memory-Ordering/ |
| A D | Tree-RCU-Memory-Ordering.rst | 13 grace-period memory ordering guarantee is provided.
35 the other of which is executed after the grace period.
49 The workhorse for RCU's grace-period memory ordering is the
75 the grace period in question.
198 newly arrived RCU callbacks against future grace periods:
382 grace period.
388 | see the start of the grace period right when it started that grace |
429 grace period, and thus a critical section that the grace period must
518 grace period.
573 cleanup is complete, the next grace period can begin.
[all …]
|
| /linux/Documentation/litmus-tests/rcu/ |
| A D | RCU+sync+free.litmus | 7 * follows a grace period, if it did not see writes that precede that grace
10 * This is a typical pattern of RCU usage, where the write before the grace
11 * period assigns a pointer, and the writes following the grace period destroy
14 * This is one implication of the RCU grace-period guarantee, which says (among
15 * other things) that an RCU read-side critical section cannot span a grace period.
|
| A D | RCU+sync+read.litmus | 6 * This litmus test demonstrates that after a grace period, an RCU updater always
8 * read-side critical sections would have ended before the grace period ended.
10 * This is one implication of the RCU grace-period guarantee, which says (among
11 * other things) that an RCU read-side critical section cannot span a grace period.
|
| /linux/Documentation/RCU/ |
| A D | stallwarn.rst | 40 - Anything that prevents RCU's grace-period kthreads from running.
51 in which case the next RCU grace period can never complete, which
60 RCU grace periods from ever completing. Either way, the
120 No grace period, no CPU stall warnings.
149 that RCU will wait from the beginning of a grace period until it
196 task stalling the current RCU-tasks grace period.
223 interrupts during the current stalled grace period.
237 (stalled) grace period, or it might be some earlier grace period (for
247 detection passes that the grace-period kthread has made across this
288 since the grace-period kthread ran. The "jiffies_till_next_fqs"
[all …]
|
| A 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?
|
| A D | rcubarrier.rst | 66 grace period to elapse, it does not wait for the callbacks to complete.
79 a grace period to elapse, rcu_barrier() waits for all outstanding RCU
83 without waiting for a grace period to elapse.
276 are delayed for a full grace period? Couldn't this result in
324 are delayed for a full grace period? Couldn't this result in
332 a grace period from completing on non-CONFIG_PREEMPTION kernels,
334 state) before the grace period can complete. However, this is
340 switching, again preventing grace periods from completing. This
|
| A D | checklist.rst | 61 to prevent grace periods from ending prematurely, which
202 boot parameter to completely disable expedited grace periods,
264 cases where grace periods are delayed, as failing to do so can
272 those waiting for a grace period to elapse. Enforce a
280 spinning on the lock could prevent the grace period
285 RCU grace period. There are of course many other
301 number of updates per grace period.
394 Second, grace-period-detection overhead is amortized only
446 grace period has elapsed since the last time that you
462 it is absolutely *not* sufficient to wait for a grace period!
[all …]
|
| A 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
|
| A D | rculist_nulls.rst | 36 * reuse these object before the RCU grace period, we
117 very very fast (before the end of RCU grace period)
|
| A D | torture.rst | 96 incremented once per grace period subsequently -- and is freed
97 after passing through (RCU_TORTURE_PIPE_LEN-2) grace periods.
105 than in terms of grace periods. The legal number of non-zero
115 passes through a grace period. The last entry should be zero,
|
| /linux/Documentation/RCU/Design/Data-Structures/ |
| A D | Data-Structures.rst | 159 states when grace periods extend too long,
172 ignored during a given grace period.
393 beginning and the end of each grace period.
437 current expedited grace period. An expedited grace period has the same
446 expedited grace periods, respectively.
509 grace period. That pointer is stored in ``->gp_tasks`` for normal grace
529 normal grace period, and task T3 is blocking neither grace period. Note
536 grace period is waiting on a blocked task.
699 grace period.
902 each grace period.
[all …]
|
| /linux/Documentation/filesystems/ |
| A D | quota.rst | 13 softlimit but only for limited period of time. This period is called "grace
14 period" or "grace time". When grace time is over, user is not able to allocate
17 Quota limits (and amount of grace time) are set independently for each
25 When user exceeds a softlimit, runs out of grace time or reaches hardlimit,
59 than given grace period
66 longer than given grace period.
|
| /linux/Documentation/RCU/Design/Requirements/ |
| A D | Requirements.rst | 537 | grace period when some access preceding the grace period observes the |
861 manner, it is necessary to use two grace periods, where the first grace
918 happens between a pair of grace periods, then those grace periods cannot
973 given grace period, just so long as it does not overlap the entire grace
975 a pair of RCU grace periods.
1472 grace period.
1576 grace-period processing. This evasive action causes the grace period to
1891 to wait for a grace period.
2565 an SRCU grace period, that grace period is waiting on a timer, and that
2607 that this grace period will be started.
[all …]
|
| /linux/kernel/rcu/ |
| A D | Kconfig | 154 number of cache misses incurred during RCU's grace-period
173 bool "Accelerate last non-dyntick-idle CPU's grace periods"
182 hand, this option increases the duration of RCU grace periods,
186 don't care about increased grace-period durations.
196 block the current preemptible RCU grace period for too long.
204 int "Milliseconds to delay boosting after RCU grace-period start"
210 a given grace period before priority-boosting preempted RCU
211 readers blocking that grace period. Note that any RCU reader
212 blocking an expedited RCU grace period is boosted immediately.
251 RCU grace periods. Given that a reasonable setting of
|
| A D | Kconfig.debug | 89 If a given RCU grace period extends more than the specified
91 RCU grace period persists, additional CPU stall warnings are
118 bool "Provide debug RCU implementation with short grace periods"
124 grace periods, making them as short as it can. This limits
|
| /linux/Documentation/litmus-tests/ |
| A D | README | 34 Both the above litmus tests demonstrate the RCU grace period guarantee
35 that an RCU read-side critical section can never span a grace period.
|
| /linux/fs/nfs_common/ |
| A D | built-in.a | 3 grace.o/
|
| A D | Makefile | 9 obj-$(CONFIG_GRACE_PERIOD) += grace.o
|
| A D | .built-in.a.cmd | 1 …64/bin/aarch64-linux-gnu-ar cDPrST fs/nfs_common/built-in.a fs/nfs_common/grace.o fs/nfs_common/nf…
|
| A D | .grace.o.cmd | 1 …grace.o := /usr/bin/ccache /home/test/workspace/code/optee_3.16/build/../toolchains/aarch64/bin/aa…
3 source_fs/nfs_common/grace.o := fs/nfs_common/grace.c
5 deps_fs/nfs_common/grace.o := \
1277 fs/nfs_common/grace.o: $(deps_fs/nfs_common/grace.o)
1279 $(deps_fs/nfs_common/grace.o):
|
| /linux/drivers/firewire/ |
| A 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/tools/memory-model/Documentation/ |
| A D | simple.txt | 62 takes this approach for much of its grace-period processing and also
64 single-threaded grace-period processing is use of batching, where all
65 updates that accumulated during one grace period are handled by the
66 next one. In other words, slowing down grace-period processing makes
128 locking to report quiescent states up the grace-period combining tree.
|
| /linux/Documentation/admin-guide/nfs/ |
| A D | nfsd-admin-interfaces.rst | 25 On startup, nfsd and lockd grace periods start. nfsd is shut down by a write of
|
| /linux/fs/xfs/ |
| A D | xfs_dquot.h | 251 time64_t xfs_dquot_set_grace_period(time64_t grace);
|