Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753266Ab2FMMsE (ORCPT ); Wed, 13 Jun 2012 08:48:04 -0400 Received: from merlin.infradead.org ([205.233.59.134]:36812 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750987Ab2FMMsB convert rfc822-to-8bit (ORCPT ); Wed, 13 Jun 2012 08:48:01 -0400 Message-ID: <1339591666.8980.26.camel@twins> Subject: Re: [RFC 3/4] ARM: topology: Update cpu_power according to DT information From: Peter Zijlstra To: Amit Kucheria Cc: Vincent Guittot , Jean Pihet , linux@arm.linux.org.uk, devicetree-discuss@lists.ozlabs.org, linux-kernel@vger.kernel.org, rob.herring@calxeda.com, linaro-dev@lists.linaro.org, linux-arm-kernel@lists.infradead.org Date: Wed, 13 Jun 2012 14:47:46 +0200 In-Reply-To: References: <1339502524-10265-1-git-send-email-vincent.guittot@linaro.org> <1339502524-10265-4-git-send-email-vincent.guittot@linaro.org> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1058 Lines: 20 On Wed, 2012-06-13 at 18:14 +0530, Amit Kucheria wrote: > Various discussions around power-aware scheduling have amplified the > need for the scheduler to have some knowledge of DVFS. This would then > require the scheduler to track 'cpu_power' ( = max power) and perhaps > a new variable 'current_power' that is changed by the DVFS framework. Note that capacity is in fact a better term -- not to be confused with the capacity as currently in use within the load-balancer. Luckily there's no way to read that an not be confused.. uhmm :-) > > The first goal, though, is to make sure that the scheduler can handle > different cpu_power values due to asymmetric cores. I would think the very first goal was to do a simple packing balancer before doing silly things with asymmetric setups.. but what do I know. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/