On 14 May 2014 23:35, Stratos Karafotis <strat...@semaphore.gr> wrote: > Many drivers keep frequencies in frequency table in ascending > or descending order. When governor tries to change to policy->min > or policy->max respectively then the cpufreq_frequency_table_target > could return on first iteration. This will save some iteration cycles. > > So, break out early when a frequency in cpufreq_frequency_table > equals to target one. > > Testing this during kernel compilation using ondemand governor > with a frequency table in ascending order, the > cpufreq_frequency_table_target returned early on the first > iteration at about 30% of times called. > > Signed-off-by: Stratos Karafotis <strat...@semaphore.gr> > --- > drivers/cpufreq/freq_table.c | 8 ++++++-- > 1 file changed, 6 insertions(+), 2 deletions(-)
Acked-by: Viresh Kumar <viresh.ku...@linaro.org> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
