sched-energy.rst (666fab4a3ea143315a9c059fad9f3a0f1365d54b) | sched-energy.rst (5a64f775691647c242aa40d34f3512e7b179a921) |
---|---|
1======================= 2Energy Aware Scheduling 3======================= 4 51. Introduction 6--------------- 7 8Energy Aware Scheduling (or EAS) gives the scheduler the ability to predict --- 336 unchanged lines hidden (view full) --- 345EAS uses the EM of a platform to estimate the impact of scheduling decisions on 346energy. So, your platform must provide power cost tables to the EM framework in 347order to make EAS start. To do so, please refer to documentation of the 348independent EM framework in Documentation/power/energy-model.rst. 349 350Please also note that the scheduling domains need to be re-built after the 351EM has been registered in order to start EAS. 352 | 1======================= 2Energy Aware Scheduling 3======================= 4 51. Introduction 6--------------- 7 8Energy Aware Scheduling (or EAS) gives the scheduler the ability to predict --- 336 unchanged lines hidden (view full) --- 345EAS uses the EM of a platform to estimate the impact of scheduling decisions on 346energy. So, your platform must provide power cost tables to the EM framework in 347order to make EAS start. To do so, please refer to documentation of the 348independent EM framework in Documentation/power/energy-model.rst. 349 350Please also note that the scheduling domains need to be re-built after the 351EM has been registered in order to start EAS. 352 |
353EAS uses the EM to make a forecasting decision on energy usage and thus it is 354more focused on the difference when checking possible options for task 355placement. For EAS it doesn't matter whether the EM power values are expressed 356in milli-Watts or in an 'abstract scale'. |
|
353 | 357 |
358 |
|
3546.3 - Energy Model complexity 355^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 356 357The task wake-up path is very latency-sensitive. When the EM of a platform is 358too complex (too many CPUs, too many performance domains, too many performance 359states, ...), the cost of using it in the wake-up path can become prohibitive. 360The energy-aware wake-up algorithm has a complexity of: 361 --- 61 unchanged lines hidden --- | 3596.3 - Energy Model complexity 360^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 361 362The task wake-up path is very latency-sensitive. When the EM of a platform is 363too complex (too many CPUs, too many performance domains, too many performance 364states, ...), the cost of using it in the wake-up path can become prohibitive. 365The energy-aware wake-up algorithm has a complexity of: 366 --- 61 unchanged lines hidden --- |