From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752447AbbCXKw3 (ORCPT ); Tue, 24 Mar 2015 06:52:29 -0400 Received: from foss.arm.com ([217.140.101.70]:47903 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752141AbbCXKw1 (ORCPT ); Tue, 24 Mar 2015 06:52:27 -0400 Date: Tue, 24 Mar 2015 10:52:59 +0000 From: Morten Rasmussen To: Peter Zijlstra Cc: "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" , Juri Lelli , "linux-kernel@vger.kernel.org" Subject: Re: [RFCv3 PATCH 29/48] sched: Highest energy aware balancing sched_domain level pointer Message-ID: <20150324105259.GD18994@e105550-lin.cambridge.arm.com> References: <1423074685-6336-1-git-send-email-morten.rasmussen@arm.com> <1423074685-6336-30-git-send-email-morten.rasmussen@arm.com> <20150323161606.GK23123@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150323161606.GK23123@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 23, 2015 at 04:16:06PM +0000, Peter Zijlstra wrote: > On Wed, Feb 04, 2015 at 06:31:06PM +0000, Morten Rasmussen wrote: > > Add another member to the family of per-cpu sched_domain shortcut > > pointers. This one, sd_ea, points to the highest level at which energy > > model is provided. At this level and all levels below all sched_groups > > have energy model data attached. > > Here might be a good point to discuss what it means for the topology to > have partial energy model information. Partial energy model information is supported as in you can have energy model data for just lower level sched domains and leave scheduling between higher level sched_domains to be done the non-energy-aware (current) way. For example, have energy-aware scheduling working within each socket on a multi-socket system and let normal performance (spreading) load-balancing work between sockets. Or within a NUMA node and not between NUMA nodes as I mentioned in my reply to the next patch.