From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752350AbbCZKmH (ORCPT ); Thu, 26 Mar 2015 06:42:07 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:58750 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752040AbbCZKmD (ORCPT ); Thu, 26 Mar 2015 06:42:03 -0400 Date: Thu, 26 Mar 2015 11:41:50 +0100 From: Peter Zijlstra To: Juri Lelli Cc: Morten Rasmussen , "mingo@redhat.com" , "vincent.guittot@linaro.org" , Dietmar Eggemann , "yuyang.du@intel.com" , "preeti@linux.vnet.ibm.com" , "mturquette@linaro.org" , "nico@linaro.org" , "rjw@rjwysocki.net" , "linux-kernel@vger.kernel.org" Subject: Re: [RFCv3 PATCH 33/48] sched: Energy-aware wake-up task placement Message-ID: <20150326104150.GW21418@twins.programming.kicks-ass.net> References: <1423074685-6336-1-git-send-email-morten.rasmussen@arm.com> <1423074685-6336-34-git-send-email-morten.rasmussen@arm.com> <20150324163503.GZ23123@twins.programming.kicks-ass.net> <5512F7F2.2010705@arm.com> <20150325181413.GT21418@twins.programming.kicks-ass.net> <5513DDA4.10802@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5513DDA4.10802@arm.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 26, 2015 at 10:21:24AM +0000, Juri Lelli wrote: > - what about other sched classes? I know that this is very premature, > but I can help but thinking that we'll need to do some sort of > aggregation of requests, and if we put triggers in very specialized > points we might lose some of the sched classes separation So for deadline we can do P state selection (as you're well aware) based on the requested utilization. Not sure what to do for fifo/rr though, they lack much useful information (as always). Now if we also look ahead to things like the ACPI CPPC stuff we'll see that CFS and DL place different requirements on the hints. Where CFS would like to hint a max perf (the hardware going slower due to the code consisting of mostly stalls is always fine from a best effort energy pov), the DL stuff would like to hint a min perf, seeing how it 'needs' to provide a QoS. So we either need to carry this information along in a 'generic' way between the various classes or put the hinting in every class. But yes, food for thought for sure.