| /linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| H A D | Expedited-Grace-Periods.rst | 8 This document describes RCU's expedited grace periods.
9 Unlike RCU's normal grace periods, which accept long latencies to attain
10 high efficiency and minimal disturbance, expedited grace periods accept
20 The expedited RCU grace periods cannot be accused of being subtle,
23 grace period.
24 The one saving grace is that the hammer has grown a bit smaller
32 state, the expedited grace period has completed.
43 expedited grace period is shown in the following diagram:
54 Otherwise, the expedited grace period will use
72 block the current expedited grace period until it resumes and finds its
[all …]
|
| /linux/Documentation/RCU/Design/Memory-Ordering/ |
| H A D | Tree-RCU-Memory-Ordering.rst | 13 grace-period memory ordering guarantee is provided.
18 RCU grace periods provide extremely strong memory-ordering guarantees
20 Any code that happens after the end of a given RCU grace period is guaranteed
21 to see the effects of all accesses prior to the beginning of that grace
23 Similarly, any code that happens before the beginning of a given RCU grace
25 of that grace period that are within RCU read-side critical sections.
34 two phases, one of which is executed before the grace period and
35 the other of which is executed after the grace period.
49 The workhorse for RCU's grace-period memory ordering is the
73 network among all CPUs that were in any way involved in the grace
[all …]
|
| /linux/Documentation/litmus-tests/rcu/ |
| H 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.
|
| H 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/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 20 to execute extremely quickly, while also processing the RCU grace periods
46 grace periods are completed at the tree's root ``rcu_node``
48 A grace period can be completed at the root once every CPU
51 Once a grace period has completed, record of that fact is propagated
102 and scalability benefits of partitioning, even though RCU grace-period
112 there are in the system, at most 64 quiescent-state reports per grace
121 RCU updaters wait for normal grace periods by registering RCU callbacks,
125 while they are waiting for a grace period to elapse, as shown in the
145 example, awareness of the start or end of a given RCU grace period
155 ``rcu_node`` and ``rcu_data`` structures, tracks grace periods,
[all …]
|
| /linux/Documentation/filesystems/ |
| H 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/ |
| H 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 listRCU.rst for more
29 - How can the updater tell when a grace period has completed
46 critical sections. These variants of RCU detect grace periods
50 thing at a time, why should I wait for a grace period?
|
| H A D | UP.rst | 23 after a grace period.
45 RCU usage, since call_rcu() must wait for a grace period to elapse.
63 call_rcu() invocation a full grace period later.
91 grace period has elapsed since those callbacks were queued. This is
102 infrastructure *must* respect grace periods, and *must* invoke callbacks
151 end of the grace period, which would come as a nasty shock to
|
| H A D | checklist.rst | 61 to prevent grace periods from ending prematurely, which
223 kernel boot parameter to completely disable expedited grace
247 srcu_struct. The rules for the expedited RCU grace-period-wait
291 primitive is that it automatically self-limits: if grace periods
295 cases where grace periods are delayed, as failing to do so can
303 those waiting for a grace period to elapse. Enforce a
311 spinning on the lock could prevent the grace period
316 RCU grace period. There are of course many other
332 number of updates per grace period.
442 Second, grace-period-detection overhead is amortized only
[all …]
|
| H A D | rculist_nulls.rst | 47 * reuse these object before the RCU grace period, we
125 very very fast (before the end of RCU grace period)
|
| H A D | rcuref.rst | 120 until after a grace period has elapsed following removal. This means that
|
| H A D | whatisRCU.rst | 246 of automatically limiting update rate should grace periods
457 * frees up the old structure after a grace period.
532 In the example above, foo_update_a() blocks until a grace period elapses.
541 This function invokes func(head) after a grace period has elapsed.
559 * frees up the old structure after a grace period.
995 been updated, and then a grace period has passed. Every remaining
1277 e. Do you need RCU grace periods to complete even in the face of
1396 grace periods short if need be (for example, if running
|
| /linux/Documentation/litmus-tests/ |
| H A D | README | 79 Both the above litmus tests demonstrate the RCU grace period guarantee
80 that an RCU read-side critical section can never span a grace period.
|
| /linux/tools/memory-model/Documentation/ |
| H 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.
|
| H A D | explanation.txt | 930 grace periods obey the rules of RCU, in particular, the
1517 rests on two concepts: grace periods and read-side critical sections.
1519 A grace period is the span of time occupied by a call to
1527 span a full grace period. In more detail, the Guarantee says:
1529 For any critical section C and any grace period G, at least
1541 before and end after a grace period.
1568 P1's grace period, contrary to part (2) of the Guarantee. On the
1571 the grace period, contrary to part (1). Together the results violate
1577 starts before a grace period does then the critical section's CPU will
1579 some time before the grace period's synchronize_rcu() call returns.
[all …]
|
| H A D | ordering.txt | 65 o RCU's grace-period primitives.
113 Finally, RCU's grace-period primitives provide full ordering. These
117 Furthermore, RCU's grace-period primitives can only be invoked in
118 sleepable contexts. Therefore, RCU's grace-period primitives are
380 they interact only with the corresponding grace-period primitives.
|
| H A D | litmus-tests.txt | 850 31 synchronize_rcu(); // Wait one grace period.
870 waits for an RCU grace period to elapse, and finally line 32 emulates
|
| /linux/Documentation/admin-guide/nfs/ |
| H A D | nfsd-admin-interfaces.rst | 25 On startup, nfsd and lockd grace periods start. nfsd is shut down by a write of
|
| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | kvm.sh | 93 echo " --shutdown-grace seconds"
253 --shutdown-grace)
254 checkarg --shutdown-grace "(seconds)" "$#" "$2" '^[0-9]*$' '^error'
|
| /linux/Documentation/core-api/ |
| H A 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
520 until after the RCU grace period.
524 after the RCU grace period.
562 Obsolete blocks and leaves are freed up after an RCU grace period has passed,
|
| /linux/tools/memory-model/ |
| H A D | linux-kernel.cat | 147 * Any sequence containing at least as many grace periods as RCU read-side
150 * Likewise for SRCU grace periods and read-side critical sections, provided
|
| /linux/Documentation/admin-guide/ |
| H A D | kernel-parameters.txt | 3538 lockd.nlm_grace_period=P [NFS] Assign grace period.
3575 there is a high probability of an RCU grace period
5627 for the kthreads that mediate grace periods; and
5667 If triggered before the RCU grace-period machinery
5677 RCU grace-period cleanup.
5681 RCU grace-period initialization.
5685 RCU grace-period pre-initialization, that is,
5690 Set delay from grace-period initialization to
5702 given grace period before RCU starts
5718 and for the RCU grace-period kthreads (rcu_bh,
[all …]
|
| /linux/fs/xfs/ |
| H A D | xfs_dquot.c | 166 time64_t grace) in xfs_dquot_set_grace_period() argument
168 return clamp_t(time64_t, grace, XFS_DQ_GRACE_MIN, XFS_DQ_GRACE_MAX); in xfs_dquot_set_grace_period()
|
| /linux/Documentation/security/keys/ |
| H A D | core.rst | 1366 to set the pointer and dispose of the old contents after a grace period.
|