Lines Matching refs:that
5 output that summarizes counters and state. This information is useful for
21 Note that rcu/rcu_preempt is only present for CONFIG_PREEMPT_RCU.
23 so that activity for both appears in rcu/rcu_sched.
32 The first line shows the number of rcutorture tests that have completed
35 update cycles that the current test has started, or zero if there is
51 Displays counts of the reasons rcu_pending() decided that RCU had
74 no output for CPUs that have never been online, which can be
78 o "c" is the count of grace periods that this CPU believes have
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
91 period that it is aware of, otherwise, the CPU believes that it
94 o "pq" indicates that this CPU has passed through a quiescent state
96 "1" and "c" different than "g", which indicates that although
98 CPU has not yet reported that fact, (2) some other CPU has not
101 o "qp" indicates that RCU still expects a quiescent state from
105 o "dt" is the current value of the dyntick counter that is incremented
117 o "df" is the number of times that some other CPU has forced a
121 o "of" is the number of times that some other CPU has forced a
124 turns out that offlining and onlining a CPU can take several grace
126 when RCU believes that the CPU is online when it really is not.
127 Please note that erring in the other direction (RCU believing a
133 that are known to RCU to only be freeing memory, and the number
136 grace-period processing that they are in (new, waiting for
143 "N" Indicates that there are callbacks queued that are not
148 "R" Indicates that there are callbacks queued that are
151 "W" Indicates that there are callbacks queued that are
154 "D" Indicates that there are callbacks queued that have
156 thus waiting to be invoked. Note that callbacks in
159 that have been removed from the rcu_data structures
170 o "ci" is the number of RCU callbacks that have been invoked for
171 this CPU. Note that ci+nci+ql is the number of callbacks that have
174 o "nci" is the number of RCU callbacks that have been offloaded from
179 o "co" is the number of RCU callbacks that have been orphaned due to
183 o "ca" is the number of RCU callbacks that have been adopted by this
184 CPU due to other CPUs going offline. Note that ci+co-ca+ql is
226 The number after the final slash is the CPU that the kthread
232 the number of times that this CPU's per-CPU kthread has gone
244 o "s" is the sequence number, with an odd number indicating that
247 o "wd0", "wd1", "wd2", and "wd3" are the number of times that an
248 attempt to start an expedited grace period found that someone
249 else had completed an expedited grace period that satisfies the
252 o "n" is number of times that a concurrent CPU-hotplug operation
257 o "sc" is the number of times that the attempt to start a
267 o "completed" is the number of grace periods that have completed.
268 It is comparable to the "c" field from rcu/rcudata in that a
270 that the corresponding RCU grace period has completed.
272 o "gpnum" is the number of grace periods that have started. It is
273 similarly comparable to the "g" field from rcu/rcudata in that
274 a CPU whose "g" field matches the value of "gpnum" is aware that
282 o "age" is the number of jiffies that the current grace period
306 along. Note that CPUs in idle mode throughout the grace period
311 Yes, Paul did run into a number of problems that turned out to
321 between "nfqs" and "nfqsng", or the number of times that
324 o "fqlh" is the number of calls to force_quiescent_state() that
332 Note that there might be either one, two, three, or even four
341 set for each entity in the next lower level that has
344 The qsmaskinit will have one bit for each entity that is
346 The value of qsmaskinit is assigned to that of qsmask
351 indicates that at least one task blocked in an RCU
353 period, while a "E" preceding the ">" indicates that
356 A "T" character following the ">" indicates that at
361 does not hold, so that "..>." indicates that no tasks
371 has "0:7", indicating that it covers CPUs 0 through 7.
374 next higher level rcu_node structure that this rcu_node
376 ^1" has a "1" in this position, indicating that it
397 o "np" is the number of times that __rcu_pending() has been invoked
400 o "qsp" is the number of times that the RCU was waiting for a
403 o "rpq" is the number of times that the CPU had passed through
406 o "cbr" is the number of times that this CPU had RCU callbacks
407 that had passed through a grace period, and were thus ready
410 o "cng" is the number of times that this CPU needed another
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,
419 o "ndw" is the number of times that a wakeup of an rcuo
423 o "nn" is the number of times that this CPU needed nothing.
444 "T" This indicates that there are some tasks that blocked
448 "N" This indicates that some of the blocked tasks are preventing
452 "E" This indicates that some of the blocked tasks are preventing
455 "B" This indicates that some of the blocked tasks are in
485 that was blocking both an expedited and a normal grace period,
491 o "bt" is the low-order 16 bits of the value that the jiffies
492 counter will have when we next start boosting, assuming that
511 period that never had blocked. If it is already running, it