Lines Matching refs:grace
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.
124 turns out that offlining and onlining a CPU can take several grace
136 grace-period processing that they are in (new, waiting for
137 grace period to start, waiting for grace period to end, ready
144 ready to be handled by the next grace period, and thus
145 will be handled by the grace period following the next
149 ready to be handled by the next grace period.
152 waiting on the current grace period.
155 already been handled by a prior grace period, and are
245 an expedited grace period is in progress.
248 attempt to start an expedited grace period found that someone
249 else had completed an expedited grace period that satisfies the
253 forced a fallback to a normal grace period.
258 new expedited grace period succeeded.
267 o "completed" is the number of grace periods that have completed.
270 that the corresponding RCU grace period has completed.
272 o "gpnum" is the number of grace periods that have started. It is
275 the corresponding RCU grace period has started.
277 If these two fields are equal, then there is no grace period
279 if the two fields differ (as they are above), then an RCU grace
282 o "age" is the number of jiffies that the current grace period
283 has extended for, or zero if there is no grace period currently
286 o "max" is the age in jiffies of the longest-duration grace period
304 o "jfq" is the number of jiffies remaining for this grace period
306 along. Note that CPUs in idle mode throughout the grace period
318 where there wasn't actually a grace period active. This can
319 no longer happen due to grace-period processing being pushed
342 not yet checked in for the current grace period ("e"
345 currently expected to check in during each grace period.
347 at the beginning of each grace period.
352 read-side critical section blocks the current grace
355 section blocks the current expedited grace period.
359 grace period (expedited or normal) is inconvenienced.
407 that had passed through a grace period, and were thus ready
411 grace period while RCU was idle.
413 o "gpc" is the number of times that an old grace period had
416 o "gps" is the number of times that a new grace period had started,
449 the current normal (non-expedited) grace period from
453 the current expedited grace period from completing.
481 expedited grace period.
484 normal (non-expedited) grace period. When boosting a task
485 that was blocking both an expedited and a normal grace period,
493 the current grace period does not end beforehand. This is
504 current grace period, whether expedited or otherwise.
507 had already been initiated for the current grace period.
510 was at least one task blocking the current non-expedited grace
518 reasons, e.g., the grace period ended first.
536 for an RCU grace period or waiting to be invoked. This is the
538 short-circuiting of grace period in those two cases.