From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755043AbbIHPdV (ORCPT ); Tue, 8 Sep 2015 11:33:21 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:34064 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754430AbbIHPdP (ORCPT ); Tue, 8 Sep 2015 11:33:15 -0400 Date: Tue, 8 Sep 2015 17:33:00 +0200 From: Peter Zijlstra To: Morten Rasmussen Cc: Vincent Guittot , Dietmar Eggemann , Steve Muckle , "mingo@redhat.com" , "daniel.lezcano@linaro.org" , "yuyang.du@intel.com" , "mturquette@baylibre.com" , "rjw@rjwysocki.net" , Juri Lelli , "sgurrappadi@nvidia.com" , "pang.xunlei@zte.com.cn" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 5/6] sched/fair: Get rid of scaling utilization by capacity_orig Message-ID: <20150908153300.GK3644@twins.programming.kicks-ass.net> References: <1439569394-11974-1-git-send-email-morten.rasmussen@arm.com> <1439569394-11974-6-git-send-email-morten.rasmussen@arm.com> <55E8DD00.2030706@linaro.org> <55EDAF43.30500@arm.com> <55EDDD5A.70904@arm.com> <20150908122606.GH3644@twins.programming.kicks-ass.net> <20150908125205.GW18673@twins.programming.kicks-ass.net> <20150908143157.GA27098@e105550-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150908143157.GA27098@e105550-lin.cambridge.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 Tue, Sep 08, 2015 at 03:31:58PM +0100, Morten Rasmussen wrote: > On Tue, Sep 08, 2015 at 02:52:05PM +0200, Peter Zijlstra wrote: > > > Tricky that, LOAD_AVG_MAX very much relies on the unit being 1<<10. > > I don't get why LOAD_AVG_MAX relies on the util_avg shifting being > 1<<10, it is just the sum of the geometric series and the upper bound of > util_sum? It needs a 1024, it might just have been the 1024 ns we use a period instead of the scale unit though. The LOAD_AVG_MAX is the number where adding a next element to the series doesn't change the result anymore, so scaling it up will allow more significant elements to the series before we bottom out, which is the _N thing.