linux-kernel - Re: [RFC/RFT][PATCH 0/1] cpufreq: New governor based on scheduler-provided utilization data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 Mar 2016 15:27:10 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>
Cc:	Linux PM list <linux-pm@...r.kernel.org>,
	Juri Lelli <juri.lelli@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Steve Muckle <steve.muckle@...aro.org>
Subject: Re: [RFC/RFT][PATCH 0/1] cpufreq: New governor based on
 scheduler-provided utilization data

So I wanted to give you some feedback for this, from the scheduler maintainer's 
POV.

Looks like there are two cpufreq modernization efforts, one is this series, the 
other is Steve Muckle's:

  [RFCv7 PATCH 00/10] sched: scheduler-driven CPU frequency selection

What I'd like to see from a scheduler metrics usage POV is a single central place, 
kernel/sched/cpufreq.c, where all the high level ('governor') decisions are made.  
This is the approach Steve's series takes.

That is a central point that has ready access to the scheduler internal 
utilization metrics.

drivers/cpufreq/ would contain legacy governors plus low level drivers that do 
frequency switching with a well-defined interface.

Could you guys work out a single series that implements the sum of the two series? 
Looks like we are 90% 'there' already.

Thanks,

	Ingo