Lines Matching full:period

12 The bandwidth allowed for a group is specified using a quota and period. Within
13 each given "period" (microseconds), a task group is allocated up to "quota"
18 period when the quota is replenished.
21 cfs_quota units at each period boundary. As threads consume this bandwidth it
27 Quota and period are managed within the cpu subsystem via cgroupfs.
34 - cpu.cfs_quota_us: the total available run-time within a period (in
36 - cpu.cfs_period_us: the length of a period (in microseconds)
50 The minimum quota allowed for the quota or period is 1ms. There is also an
51 upper bound on the period length of 1s. Additional restrictions exist when
102 	a. it fully consumes its own quota within a period
103 	b. a parent's quota is fully consumed within its period
121 quota as well as the entirety of each cpu-local slice in each period. As a
123 cpuacct.usage will increase roughly equal to cfs_quota_us in each period.
132 average usage, albeit over a longer time window than a single period.  This
157 	If period is 250ms and quota is also 250ms, the group will get
161 	# echo 250000 > cpu.cfs_period_us /* period = 250ms */
165    With 500ms period and 1000ms quota, the group can get 2 CPUs worth of
169 	# echo 500000 > cpu.cfs_period_us /* period = 500ms */
171 	The larger period here allows for increased burst capacity.
175    With 50ms period, 10ms quota will be equivalent to 20% of 1 CPU::
178 	# echo 50000 > cpu.cfs_period_us /* period = 50ms */
180    By using a small period here we are ensuring a consistent latency