Lines Matching refs:of

1 Version 15 of schedstats dropped counters for some sched_yield:
5 Version 14 of schedstats includes support for sched_domains, which hit the
12 In version 14 of schedstat, there is at least one level of domain
17 sometimes balancing only between pairs of cpus.  At this time, there
23 of these will need to start with a baseline observation and then calculate
25 which does this for many of the fields is available at
38      1) # of times sched_yield() was called
43      3) # of times schedule() was called
44      4) # of times schedule() left the processor idle
47      5) # of times try_to_wake_up() was called
48      6) # of times try_to_wake_up() was called to wake up the local cpu
51      7) sum of all time spent running by tasks on this processor (in jiffies)
52      8) sum of all time spent waiting to run by tasks on this processor (in
54      9) # of timeslices run on this cpu
59 One of these is produced per domain for each cpu described. (Note that if
67 The next 24 are a variety of load_balance() statistics in grouped into types
68 of idleness (idle, busy, and newly idle):
70      1) # of times in this domain load_balance() was called when the
72      2) # of times in this domain load_balance() checked but found
74      3) # of times in this domain load_balance() tried to move one or
76      4) sum of imbalances discovered (if any) with each call to
78      5) # of times in this domain pull_task() was called when the cpu
80      6) # of times in this domain pull_task() was called even though
82      7) # of times in this domain load_balance() was called but did
84      8) # of times in this domain a busier queue was found while the
87      9) # of times in this domain load_balance() was called when the
89     10) # of times in this domain load_balance() checked but found the
91     11) # of times in this domain load_balance() tried to move one or
93     12) sum of imbalances discovered (if any) with each call to
95     13) # of times in this domain pull_task() was called when busy
96     14) # of times in this domain pull_task() was called even though the
98     15) # of times in this domain load_balance() was called but did not
100     16) # of times in this domain a busier queue was found while the cpu
103     17) # of times in this domain load_balance() was called when the
105     18) # of times in this domain load_balance() checked but found the
107     19) # of times in this domain load_balance() tried to move one or more
109     20) sum of imbalances discovered (if any) with each call to
111     21) # of times in this domain pull_task() was called when newly idle
112     22) # of times in this domain pull_task() was called even though the
114     23) # of times in this domain load_balance() was called but did not
116     24) # of times in this domain a busier queue was found while the cpu
120     25) # of times active_load_balance() was called
121     26) # of times active_load_balance() tried to move a task and failed
122     27) # of times active_load_balance() successfully moved a task
135     34) # of times in this domain try_to_wake_up() awoke a task that
137     35) # of times in this domain try_to_wake_up() moved a task to the
139     36) # of times in this domain try_to_wake_up() started passive balancing
143 schedstats also adds a new /proc/<pid>/schedstat file to include some of
148      3) # of timeslices run on this cpu
150 A program could be easily written to make use of these extra fields to
151 report on how well a particular process or set of processes is faring
152 under the scheduler's policies.  A simple version of such a program is