cpuidle: default processor.latency_factor=2
More aggressively request deep C-states. Note that the job of the OS is to minimize latency impact to expected break events such as interrupts. It is not the job of the OS to try to calculate if the C-state will reach energy break-even. The platform doesn't give the OS enough information for it to make that calculation. Thus, it is up to the platform to decide if it is worth it to go as deep as the OS requested it to, or if it should internally demote to a more shallow C-state. But the converse is not true. The platform can not promote into a deeper C-state than the OS requested else it may violate latency constraints. So it is important that the OS be aggressive in giving the platform permission to enter deep C-states. Signed-off-by: Len Brown <len.brown@intel.com>
This commit is contained in:
parent
4963f62045
commit
25de571835
|
@ -95,7 +95,7 @@ module_param(bm_history, uint, 0644);
|
|||
static int acpi_processor_set_power_policy(struct acpi_processor *pr);
|
||||
|
||||
#else /* CONFIG_CPU_IDLE */
|
||||
static unsigned int latency_factor __read_mostly = 6;
|
||||
static unsigned int latency_factor __read_mostly = 2;
|
||||
module_param(latency_factor, uint, 0644);
|
||||
#endif
|
||||
|
||||
|
|
Loading…
Reference in a new issue