Lines Matching refs:of
5 Version 16 of schedstats changed the order of definitions within
6 'enum cpu_idle_type', which changed the order of [CPU_MAX_IDLE_TYPES]
7 columns in show_schedstat(). In particular the position of CPU_IDLE
8 and __CPU_NOT_IDLE changed places. The size of the array is unchanged.
10 Version 15 of schedstats dropped counters for some sched_yield:
14 Version 14 of schedstats includes support for sched_domains, which hit the
21 In version 14 of schedstat, there is at least one level of domain
26 sometimes balancing only between pairs of cpus. At this time, there
32 of these will need to start with a baseline observation and then calculate
34 which does this for many of the fields is available at
48 1) # of times sched_yield() was called
54 3) # of times schedule() was called
55 4) # of times schedule() left the processor idle
59 5) # of times try_to_wake_up() was called
60 6) # of times try_to_wake_up() was called to wake up the local cpu
64 7) sum of all time spent running by tasks on this processor (in nanoseconds)
65 8) sum of all time spent waiting to run by tasks on this processor (in
67 9) # of timeslices run on this cpu
72 One of these is produced per domain for each cpu described. (Note that if
80 The next 24 are a variety of sched_balance_rq() statistics in grouped into types
81 of idleness (idle, busy, and newly idle):
83 1) # of times in this domain sched_balance_rq() was called when the
85 2) # of times in this domain sched_balance_rq() checked but found
87 3) # of times in this domain sched_balance_rq() tried to move one or
89 4) sum of imbalances discovered (if any) with each call to
91 5) # of times in this domain pull_task() was called when the cpu
93 6) # of times in this domain pull_task() was called even though
95 7) # of times in this domain sched_balance_rq() was called but did
97 8) # of times in this domain a busier queue was found while the
99 9) # of times in this domain sched_balance_rq() was called when the
101 10) # of times in this domain sched_balance_rq() checked but found the
103 11) # of times in this domain sched_balance_rq() tried to move one or
105 12) sum of imbalances discovered (if any) with each call to
107 13) # of times in this domain pull_task() was called when busy
108 14) # of times in this domain pull_task() was called even though the
110 15) # of times in this domain sched_balance_rq() was called but did not
112 16) # of times in this domain a busier queue was found while the cpu
115 17) # of times in this domain sched_balance_rq() was called when the
117 18) # of times in this domain sched_balance_rq() checked but found the
119 19) # of times in this domain sched_balance_rq() tried to move one or more
121 20) sum of imbalances discovered (if any) with each call to
123 21) # of times in this domain pull_task() was called when newly idle
124 22) # of times in this domain pull_task() was called even though the
126 23) # of times in this domain sched_balance_rq() was called but did not
128 24) # of times in this domain a busier queue was found while the cpu
133 25) # of times active_load_balance() was called
134 26) # of times active_load_balance() tried to move a task and failed
135 27) # of times active_load_balance() successfully moved a task
151 34) # of times in this domain try_to_wake_up() awoke a task that
153 35) # of times in this domain try_to_wake_up() moved a task to the
155 36) # of times in this domain try_to_wake_up() started passive balancing
159 schedstats also adds a new /proc/<pid>/schedstat file to include some of
165 3) # of timeslices run on this cpu
167 A program could be easily written to make use of these extra fields to
168 report on how well a particular process or set of processes is faring
169 under the scheduler's policies. A simple version of such a program is