Lines Matching full:of

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