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
70 Quota, period and burst are managed within the cpu subsystem via cgroupfs.
77 - cpu.cfs_quota_us: run-time replenished within a period (in microseconds)
78 - cpu.cfs_period_us: the length of a period (in microseconds)
95 period is 1ms. There is also an upper bound on the period length of 1s.
155 	a. it fully consumes its own quota within a period
156 	b. a parent's quota is fully consumed within its period
174 quota as well as the entirety of each cpu-local slice in each period. As a
176 cpuacct.usage will increase roughly equal to cfs_quota_us in each period.
185 average usage, albeit over a longer time window than a single period.  This
210 	If period is 250ms and quota is also 250ms, the group will get
214 	# echo 250000 > cpu.cfs_period_us /* period = 250ms */
218    With 500ms period and 1000ms quota, the group can get 2 CPUs worth of
222 	# echo 500000 > cpu.cfs_period_us /* period = 500ms */
224 	The larger period here allows for increased burst capacity.
228    With 50ms period, 10ms quota will be equivalent to 20% of 1 CPU::
231 	# echo 50000 > cpu.cfs_period_us /* period = 50ms */
233    By using a small period here we are ensuring a consistent latency
239    With 50ms period, 20ms quota will be equivalent to 40% of 1 CPU.
243 	# echo 50000 > cpu.cfs_period_us /* period = 50ms */