Lines Matching full:cpus

9 the impact of its decisions on the energy consumed by CPUs. EAS relies on an
10 Energy Model (EM) of the CPUs to select an energy efficient CPU for each task,
59 In short, EAS changes the way CFS tasks are assigned to CPUs. When it is time
64 knowledge about the platform's topology, which include the 'capacity' of CPUs,
72 differentiate CPUs with different computing throughput. The 'capacity' of a CPU
76 tasks and CPUs computed by the Per-Entity Load Tracking (PELT) mechanism. Thanks
79 energy trade-offs. The capacity of CPUs is provided via arch-specific code
99     Let us consider a platform with 12 CPUs, split in 3 performance domains
102 	          CPUs:   0 1 2 3 4 5 6 7 8 9 10 11
108     containing 6 CPUs. The two root domains are denoted rd1 and rd2 in the
143 looks at the current utilization landscape of the CPUs and adjusts it to
152     composed of two CPUs each. CPU0 and CPU1 are little CPUs; CPU2 and CPU3
158     The current utilization landscape of the CPUs is depicted on the graph
159     below. CPUs 0-3 have a util_avg of 400, 100, 600 and 500 respectively
184     find_energy_efficient_cpu() will first look for the CPUs with the
249 Big CPUs are generally more power hungry than the little ones and are thus used
250 mainly when a task doesn't fit the littles. However, little CPUs aren't always
251 necessarily more energy-efficient than big CPUs. For some systems, the high OPPs
252 of the little CPUs can be less energy-efficient than the lowest OPPs of the
253 bigs, for example. So, if the little CPUs happen to have enough utilization at
258 And even in the case where all OPPs of the big CPUs are less energy-efficient
259 than those of the little, using the big CPUs for a small task might still, under
264 running on a little, but it won't impact the other tasks of the little CPUs
266 consumed by CPUs, the extra cost of running that one task on a big core can be
267 smaller than the cost of raising the OPP on the little CPUs for all the other
272 CPUs of the system. Thanks to its EM-based design, EAS should cope with them
285 throughput. In order to avoid hurting performance with EAS, CPUs are flagged as
287 capacity. As long as no CPUs are over-utilized in a root domain, load balancing
289 the most energy efficient CPUs of the system more than the others if that can be
295     a. there is some idle time on all CPUs, so the utilization signals used by
320 Energy Aware Scheduling depends on the CPUs of the system having specific
362 EAS does not impose any complexity limit on the number of PDs/OPPs/CPUs but
363 restricts the number of CPUs to EM_MAX_NUM_CPUS to prevent overflows during
370 EAS tries to predict at which OPP will the CPUs be running in the close future
372 of CPUs follow their utilization.
388 In order to make accurate prediction across CPUs and for all performance
402 CPUs, which can actually be counter-productive for both performance and energy.