summaryrefslogtreecommitdiffstats
path: root/include/linux/cpufreq.h
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2019-03-28 11:33:21 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2019-04-08 11:25:32 +0200
commit9eca544b1491df90ea7102a7ed14acc3c562d97b (patch)
tree58381c6c173afd3c004fde74d3da2da79587e1e9 /include/linux/cpufreq.h
parent540a375822a40675868c5f62ae57b608a579e56a (diff)
downloadlinux-9eca544b1491df90ea7102a7ed14acc3c562d97b.tar.bz2
cpufreq: schedutil: Simplify iowait boosting
There is not reason for the minimum iowait boost value in the schedutil cpufreq governor to depend on the available range of CPU frequencies. In fact, that dependency is generally confusing, because it causes the iowait boost to behave somewhat differently on CPUs with the same maximum frequency and different minimum frequencies, for example. For this reason, replace the min field in struct sugov_cpu with a constant and choose its values to be 1/8 of SCHED_CAPACITY_SCALE (for consistency with the intel_pstate driver's internal governor). [Note that policy->cpuinfo.max_freq will not be a constant any more after a subsequent change, so this change is depended on by it.] Link: https://lore.kernel.org/lkml/20190305083202.GU32494@hirez.programming.kicks-ass.net/T/#ee20bdc98b7d89f6110c0d00e5c3ee8c2ced93c3d Suggested-by: Peter Zijlstra <peterz@infradead.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'include/linux/cpufreq.h')
0 files changed, 0 insertions, 0 deletions