Re: [PATCH 4/4] sched: cpufreq_cfs: pelt-based cpu frequency scaling

2015-05-07 Thread Peter Zijlstra
On Wed, May 06, 2015 at 09:17:25PM -0700, Michael Turquette wrote: Are you thinking of placing the hook somewhere such as update_entity_load_avg? Nah, I was more thinking of Morten's series where we already compute the utilization for the energy aware scheduling reasons. -- To unsubscribe from

Re: [PATCH 4/4] sched: cpufreq_cfs: pelt-based cpu frequency scaling

2015-05-07 Thread Juri Lelli
Hi Mike, On 07/05/15 05:17, Michael Turquette wrote: Quoting Peter Zijlstra (2015-05-06 05:22:40) On Tue, May 05, 2015 at 11:23:47AM -0700, Michael Turquette wrote: Quoting Peter Zijlstra (2015-05-05 02:00:42) On Mon, May 04, 2015 at 03:10:41PM -0700, Michael Turquette wrote: This policy is

Re: [PATCH 4/4] sched: cpufreq_cfs: pelt-based cpu frequency scaling

2015-05-07 Thread Michael Turquette
Quoting Juri Lelli (2015-05-07 03:49:27) Hi Mike, On 07/05/15 05:17, Michael Turquette wrote: Quoting Peter Zijlstra (2015-05-06 05:22:40) On Tue, May 05, 2015 at 11:23:47AM -0700, Michael Turquette wrote: Quoting Peter Zijlstra (2015-05-05 02:00:42) On Mon, May 04, 2015 at 03:10:41PM

Re: [PATCH 4/4] sched: cpufreq_cfs: pelt-based cpu frequency scaling

2015-05-06 Thread Peter Zijlstra
On Tue, May 05, 2015 at 11:23:47AM -0700, Michael Turquette wrote: Quoting Peter Zijlstra (2015-05-05 02:00:42) On Mon, May 04, 2015 at 03:10:41PM -0700, Michael Turquette wrote: This policy is implemented using the cpufreq governor interface for two main reasons: 1) re-using the

Re: [PATCH 4/4] sched: cpufreq_cfs: pelt-based cpu frequency scaling

2015-05-05 Thread Juri Lelli
Hi Peter, thanks a lot for the fast reply! :) On 05/05/15 10:00, Peter Zijlstra wrote: On Mon, May 04, 2015 at 03:10:41PM -0700, Michael Turquette wrote: This policy is implemented using the cpufreq governor interface for two main reasons: 1) re-using the cpufreq machine drivers without

Re: [PATCH 4/4] sched: cpufreq_cfs: pelt-based cpu frequency scaling

2015-05-05 Thread Peter Zijlstra
On Mon, May 04, 2015 at 03:10:41PM -0700, Michael Turquette wrote: This policy is implemented using the cpufreq governor interface for two main reasons: 1) re-using the cpufreq machine drivers without using the governor interface is hard. 2) using the cpufreq interface allows us to switch

Re: [PATCH 4/4] sched: cpufreq_cfs: pelt-based cpu frequency scaling

2015-05-05 Thread Peter Zijlstra
*groan* do _NOT_ cross-post with moderated lists, like this eas drivel. Also, you typoed 'linaro-kernel@..' getting me even more noise for every reply. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo

Re: [PATCH 4/4] sched: cpufreq_cfs: pelt-based cpu frequency scaling

2015-05-05 Thread Peter Zijlstra
On Mon, May 04, 2015 at 03:10:41PM -0700, Michael Turquette wrote: For those that are very curious, there were recently two previous postings of these patches to the public eas-dev mailing list. Of interest in those threads is the discussion around using a utilization threadhold versus purely

[PATCH 4/4] sched: cpufreq_cfs: pelt-based cpu frequency scaling

2015-05-04 Thread Michael Turquette
Scheduler-driven cpu frequency selection is desirable as part of the on-going effort to make the scheduler better aware of energy consumption. No piece of the Linux kernel has a better view of the factors that affect a cpu frequency selection policy than the scheduler[0], and this patch is an