From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756777AbcBWBdU (ORCPT ); Mon, 22 Feb 2016 20:33:20 -0500 Received: from mail-pf0-f177.google.com ([209.85.192.177]:34407 "EHLO mail-pf0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756681AbcBWBdS (ORCPT ); Mon, 22 Feb 2016 20:33:18 -0500 Subject: Re: [RFCv7 PATCH 00/10] sched: scheduler-driven CPU frequency selection To: Peter Zijlstra , Ingo Molnar , "Rafael J. Wysocki" References: <1456190570-4475-1-git-send-email-smuckle@linaro.org> Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, Vincent Guittot , Morten Rasmussen , Dietmar Eggemann , Juri Lelli , Patrick Bellasi , Michael Turquette From: Steve Muckle X-Enigmail-Draft-Status: N1110 Message-ID: <56CBB6DC.8030809@linaro.org> Date: Mon, 22 Feb 2016 17:33:16 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <1456190570-4475-1-git-send-email-smuckle@linaro.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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