Lines Matching full:period

11 The bandwidth allowed for a group is specified using a quota and period. Within
12 each given "period" (microseconds), a task group is allocated up to "quota"
17 period when the quota is replenished.
20 cfs_quota units at each period boundary. As threads consume this bandwidth it
26 Quota and period are managed within the cpu subsystem via cgroupfs.
28 cpu.cfs_quota_us: the total available run-time within a period (in microseconds)
29 cpu.cfs_period_us: the length of a period (in microseconds)
43 The minimum quota allowed for the quota or period is 1ms. There is also an
44 upper bound on the period length of 1s. Additional restrictions exist when
95 	a. it fully consumes its own quota within a period
96 	b. a parent's quota is fully consumed within its period
114 quota as well as the entirety of each cpu-local slice in each period. As a
116 cpuacct.usage will increase roughly equal to cfs_quota_us in each period.
125 average usage, albeit over a longer time window than a single period.  This
150 	If period is 250ms and quota is also 250ms, the group will get
154 	# echo 250000 > cpu.cfs_period_us /* period = 250ms */
158    With 500ms period and 1000ms quota, the group can get 2 CPUs worth of
162 	# echo 500000 > cpu.cfs_period_us /* period = 500ms */
164 	The larger period here allows for increased burst capacity.
168    With 50ms period, 10ms quota will be equivalent to 20% of 1 CPU::
171 	# echo 50000 > cpu.cfs_period_us /* period = 50ms */
173    By using a small period here we are ensuring a consistent latency