Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932359AbaJHNxo (ORCPT ); Wed, 8 Oct 2014 09:53:44 -0400 Received: from foss-mx-na.foss.arm.com ([217.140.108.86]:42484 "EHLO foss-mx-na.foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753859AbaJHNxn (ORCPT ); Wed, 8 Oct 2014 09:53:43 -0400 Date: Wed, 8 Oct 2014 14:53:40 +0100 From: Morten Rasmussen To: Vincent Guittot Cc: Peter Zijlstra , "mingo@redhat.com" , Dietmar Eggemann , Paul Turner , Benjamin Segall , Nicolas Pitre , Mike Turquette , "rjw@rjwysocki.net" , linux-kernel Subject: Re: [PATCH 1/7] sched: Introduce scale-invariant load tracking Message-ID: <20141008135339.GC1788@e105550-lin.cambridge.arm.com> References: <1411403047-32010-1-git-send-email-morten.rasmussen@arm.com> <1411403047-32010-2-git-send-email-morten.rasmussen@arm.com> <20140925172343.GX23693@e103034-lin> <20141002203428.GI2849@worktop.programming.kicks-ass.net> <20141008110054.GA1788@e105550-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Wed, Oct 08, 2014 at 12:21:45PM +0100, Vincent Guittot wrote: > On 8 October 2014 13:00, Morten Rasmussen wrote: > > On Thu, Oct 02, 2014 at 09:34:28PM +0100, Peter Zijlstra wrote: > >> On Thu, Sep 25, 2014 at 06:23:43PM +0100, Morten Rasmussen wrote: > >> > >> > > Why haven't you used arch_scale_freq_capacity which has a similar > >> > > purpose in scaling the CPU capacity except the additional sched_domain > >> > > pointer argument ? > >> > > >> > To be honest I'm not happy with introducing another arch-function > >> > either and I'm happy to change that. It wasn't really clear to me which > >> > functions that would remain after your cpu_capacity rework patches, so I > >> > added this one. Now that we have most of the patches for capacity > >> > scaling and scale-invariant load-tracking on the table I think we have a > >> > better chance of figuring out which ones are needed and exactly how they > >> > are supposed to work. > >> > > >> > arch_scale_load_capacity() compensates for both frequency scaling and > >> > micro-architectural differences, while arch_scale_freq_capacity() only > >> > for frequency. As long as we can use arch_scale_cpu_capacity() to > >> > provide the micro-architecture scaling we can just do the scaling in two > >> > operations rather than one similar to how it is done for capacity in > >> > update_cpu_capacity(). I can fix that in the next version. It will cost > >> > an extra function call and multiplication though. > >> > > >> > To make sure that runnable_avg_{sum, period} are still bounded by > >> > LOAD_AVG_MAX, arch_scale_{cpu,freq}_capacity() must both return a factor > >> > in the range 0..SCHED_CAPACITY_SCALE. > >> > >> I would certainly like some words in the Changelog on how and that the > >> math is still free of overflows. Clearly you've thought about it, so > >> please feel free to elucidate the rest of us :-) > > > > Sure. The easiest way to avoid introducing overflows is to ensure that > > we always scale by a factor >= 1.0. That should be true as long as > > arch_scale_{cpu,freq}_capacity() never returns anything greater than > > SCHED_CAPACITY_SCALE (= 1024 = 1.0). > > the current ARM arch_scale_cpu is in the range [1536..0] which is free > of overflow AFAICT If I'm not mistaken, that will cause an overflow in __update_task_entity_contrib(): static inline void __update_task_entity_contrib(struct sched_entity *se) { u32 contrib; /* avoid overflowing a 32-bit type w/ SCHED_LOAD_SCALE */ contrib = se->avg.runnable_avg_sum * scale_load_down(se->load.weight); contrib /= (se->avg.avg_period + 1); se->avg.load_avg_contrib = scale_load(contrib); } With arch_scale_cpu_capacity() > 1024 se->avg.runnable_avg_sum is no longer bounded by LOAD_AVG_MAX = 47742. scale_load_down(se->load.weight) == se->load.weight =< 88761. 47742 * 88761 = 4237627662 (2^32 = 4294967296) To avoid overflow se->avg.runnable_avg_sum must be less than 2^32/88761 = 48388, which means that arch_scale_cpu_capacity() must be in the range 0..48388*1024/47742 = 0..1037. I also think it is easier to have a fixed defined max scaling factor, but that might just be me. Regarding the ARM arch_scale_cpu_capacity() implementation, I think that can be changed to fit the 0..1024 range easily. Currently, it will only report a non-default (1024) capacity for big.LITTLE systems and actually enabling it (requires a certain property to be set in device tree) leads to broken load-balancing decisions. We have discussed that several times in the past. I wouldn't recommend enabling it until the load-balance code can deal with big.LITTLE compute capacities correctly. This is also why it isn't implemented by ARM64. -- 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/