From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752610AbbIPPmZ (ORCPT ); Wed, 16 Sep 2015 11:42:25 -0400 Received: from casper.infradead.org ([85.118.1.10]:53816 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751648AbbIPPmX (ORCPT ); Wed, 16 Sep 2015 11:42:23 -0400 Date: Wed, 16 Sep 2015 17:36:55 +0200 From: Peter Zijlstra To: bsegall@google.com Cc: Morten Rasmussen , Yuyang Du , Dietmar Eggemann , Vincent Guittot , Steve Muckle , "mingo@redhat.com" , "daniel.lezcano@linaro.org" , "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: <20150916153655.GE3604@twins.programming.kicks-ass.net> References: <55EDDD5A.70904@arm.com> <55EED99E.2040100@arm.com> <20150909201519.GB21833@intel.com> <20150910100727.GU3644@twins.programming.kicks-ass.net> <20150911002825.GA3014@intel.com> <20150911103059.GH27098@e105550-lin.cambridge.arm.com> <20150914125648.GJ27098@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 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 14, 2015 at 10:34:00AM -0700, bsegall@google.com wrote: > It has never been clear to me what > SCHED_LOAD_SCALE/SCHED_LOAD_SHIFT were for as opposed to NICE_0_LOAD, SCHED_LOAD_SCALE/SHIFT are the fixed point mult/shift, and NICE_0_LOAD is the load of a nice-0 task. They happen to be the same by the choice that nice-0 has a load of 1 (the only natural choice given proportional weight and hyperboles etc..). But for the fixed point math we use SCHED_LOAD_* and only when we want to explicitly use the unit load we use NICE_0_LOAD (its only used 4-5 times or so).