Lines Matching defs:energy

7885 	 * if energy aware scheduler is being used
9329  * energy_env - Utilization landscape for energy estimation.
9372  * energy cost is removed (by cpu_util()) and must be calculated
9451  * compute_energy(): Use the Energy Model to estimate the energy that @pd would
9461 	unsigned long energy;
9466 	energy = em_cpu_energy(pd->em_pd, max_util, busy_time, eenv->cpu_cap);
9468 	trace_sched_compute_energy_tp(p, dst_cpu, energy, max_util, busy_time);
9470 	return energy;
9474  * find_energy_efficient_cpu(): Find most energy-efficient target CPU for the
9478  * out which of the CPU candidates is the most energy-efficient.
9481  * all the most energy efficient CPU candidates (according to the Energy
9490  * In practice, it could be preferable from an energy standpoint to pack
9497  * of the energy savings of EAS come from the asymmetry of the system, and
9502  * NOTE: Forkees are not accepted in the energy-aware wake-up path because
9504  * forecast their impact on energy consumption. Consequently, they will be
9506  * to be energy-inefficient in some use-cases. The alternative would be to
9561 		/* Account external pressure for the energy estimation */
9631 		/* Compute the 'base' energy of the pd, without @p */
9634 		/* Evaluate the energy impact of using prev_cpu. */
9646 		/* Evaluate the energy impact of using max_spare_cap_cpu. */
9648 			/* Current best energy cpu fits better */
9654 			 * but best energy cpu has better capacity.
9668 			 * Both fit for the task but best energy cpu has lower
9669 			 * energy impact.
12139 	 * throughput. Maximize throughput, power/energy consequences are not