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

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]

Message-ID: <56CBB6DC.8030809@linaro.org>
Date:	Mon, 22 Feb 2016 17:33:16 -0800
From:	Steve Muckle <steve.muckle@...aro.org>
To:	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...hat.com>,
	"Rafael J. Wysocki" <rafael@...nel.org>
Cc:	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
	Vincent Guittot <vincent.guittot@...aro.org>,
	Morten Rasmussen <morten.rasmussen@....com>,
	Dietmar Eggemann <dietmar.eggemann@....com>,
	Juri Lelli <Juri.Lelli@....com>,
	Patrick Bellasi <patrick.bellasi@....com>,
	Michael Turquette <mturquette@...libre.com>
Subject: Re: [RFCv7 PATCH 00/10] sched: scheduler-driven CPU frequency
 selection

On 02/22/2016 05:22 PM, Steve Muckle wrote:
> Scheduler-driven CPU frequency selection hopes to exploit both
> per-task and global information in the scheduler to improve frequency
> selection policy and achieve lower power consumption, improved
> responsiveness/performance, and less reliance on heuristics and
> tunables. For further discussion of this integration see [0].
> 
> This patch series implements a cpufreq governor which collects CPU
> capacity requests from the fair, realtime, and deadline scheduling
> classes. The fair and realtime scheduling classes are modified to make
> these requests. The deadline class is not yet modified to make CPU
> capacity requests.

This RFC series does not attempt to address any of today's feedback
regarding simplifying the hooks in the scheduler - I'd like some more
time to ponder that. But I thought it important to get the latest
version of this out for discussion as soon as possible.

thanks,
Steve