Lines Matching refs:group

5   The SCHED_RT case is covered in Documentation/scheduler/sched-rt-group.txt ]
8 specification of the maximum CPU bandwidth available to a group or hierarchy.
10 The bandwidth allowed for a group is specified using a quota and period. Within
11 each given "period" (microseconds), a group is allowed to consume only up to
13 group exceeds this limit (for that period), the tasks belonging to its
17 A group's unused runtime is globally tracked, being refreshed with quota units
34 A value of -1 for cpu.cfs_quota_us indicates that the group does not have any
35 bandwidth restriction in place, such a group is described as an unconstrained
36 bandwidth group.  This represents the traditional work-conserving behavior for
46 and return the group to an unconstrained state once more.
48 Any updates to a group's bandwidth specification will result in it becoming
66 A group's bandwidth statistics are exported via 3 fields in cpu.stat.
70 - nr_throttled: Number of times the group has been throttled/limited.
72   of the group have been throttled.
86 There are two ways in which a group may become throttled:
95 1. Limit a group to 1 CPU worth of runtime.
97 	If period is 250ms and quota is also 250ms, the group will get
103 2. Limit a group to 2 CPUs worth of runtime on a multi-CPU machine.
105 	With 500ms period and 1000ms quota, the group can get 2 CPUs worth of
113 3. Limit a group to 20% of 1 CPU.