Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp972480ybx; Thu, 31 Oct 2019 03:54:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqzE43htF2iT+IiXYCboQ/mtGGhR/D0uNQstRyNXsSv0bZVXcQwLYYwt3ERs4Ppr+Wgl59sG X-Received: by 2002:a17:906:19d9:: with SMTP id h25mr3282828ejd.60.1572519289114; Thu, 31 Oct 2019 03:54:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572519289; cv=none; d=google.com; s=arc-20160816; b=0fAruuArUS3SCE8BafxsoTjySD9Clhna8OULDIvCAs3rSCJaCjE11hEdQU2hni2ihu MYVL4Whx/s0/MzNCNq/TNrodJcb4C6/8m/WxncsDbBLgVKCuGMMEYyeaG8QNs40BVdqo yMJiemMZarGAs0wWFmSx31zWuAmcbMWwraOg+VHTdzsVT7zAEd73cp2wPrsHnygLVKbl Nmxboi5G5l5qTBXNFOoPkOwG4BZykOb2mq+ZH/jUIp96+fi/cueHbCJVI7OJHYRW5cr2 MeYS713i32tMF7/3vEm8h7KvN65/S8ATtu8vR+9aNlmMiiyMj3MPnGHQ1hLjnKTuyABy 1SMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=vC2Dwg0PkEJfvcVMIQMbUJIad3hi1dKM0yxsONewgWI=; b=PHkWDJBh4Pvawx5RnJkuOf7iAFNapKT3e3wwq3RzpBVw+XfxnqCe8NPRURZqIcezOt yURzFLZAok1vgIoRFJvwFmwN3zc2orbp97hmZ5bwnFcj7KtfDwiD0Gm8zy83RhCfIvtU 938royBQPbAxTw+8jEG3yYZhhJS+zQoHFTgWBmzrnN9ca2FMC3yTYduDDY6WUolsDrSR L7gbfs59ztUCcgCCBGlmnJGJhXzLnT/3gF6kUaKbJkzzvlFhc0fP7e8TyvSBqsgBJMOd 2ulnAdWqIZ+Ca/msHNEOgLtxInXPusrS6zKp33o7UvVMKN5EuH9ISeg4bJlm9FwZUaIs yslA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v6si3104655ejh.280.2019.10.31.03.54.26; Thu, 31 Oct 2019 03:54:49 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727143AbfJaKxs (ORCPT + 99 others); Thu, 31 Oct 2019 06:53:48 -0400 Received: from foss.arm.com ([217.140.110.172]:46982 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726947AbfJaKxs (ORCPT ); Thu, 31 Oct 2019 06:53:48 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id D4BB71F1; Thu, 31 Oct 2019 03:53:47 -0700 (PDT) Received: from e107158-lin.cambridge.arm.com (unknown [10.1.195.37]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 4A2483F719; Thu, 31 Oct 2019 03:53:46 -0700 (PDT) Date: Thu, 31 Oct 2019 10:53:43 +0000 From: Qais Yousef To: Peter Zijlstra Cc: Thara Gopinath , mingo@redhat.com, ionela.voinescu@arm.com, vincent.guittot@linaro.org, rui.zhang@intel.com, edubezval@gmail.com, qperret@google.com, linux-kernel@vger.kernel.org, amit.kachhap@gmail.com, javi.merino@kernel.org, daniel.lezcano@linaro.org Subject: Re: [Patch v4 4/6] sched/fair: update cpu_capcity to reflect thermal pressure Message-ID: <20191031105342.b3sl5xhysldfla3g@e107158-lin.cambridge.arm.com> References: <1571776465-29763-1-git-send-email-thara.gopinath@linaro.org> <1571776465-29763-5-git-send-email-thara.gopinath@linaro.org> <20191023122252.dz7obopab6iizy4s@e107158-lin.cambridge.arm.com> <20191028153010.GE4097@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20191028153010.GE4097@hirez.programming.kicks-ass.net> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/28/19 16:30, Peter Zijlstra wrote: > On Wed, Oct 23, 2019 at 01:28:40PM +0100, Qais Yousef wrote: > > On 10/22/19 16:34, Thara Gopinath wrote: > > > cpu_capacity relflects the maximum available capacity of a cpu. Thermal > > > pressure on a cpu means this maximum available capacity is reduced. This > > > patch reduces the average thermal pressure for a cpu from its maximum > > > available capacity so that cpu_capacity reflects the actual > > > available capacity. > > > > > > Signed-off-by: Thara Gopinath > > > --- > > > kernel/sched/fair.c | 1 + > > > 1 file changed, 1 insertion(+) > > > > > > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c > > > index 4f9c2cb..be3e802 100644 > > > --- a/kernel/sched/fair.c > > > +++ b/kernel/sched/fair.c > > > @@ -7727,6 +7727,7 @@ static unsigned long scale_rt_capacity(struct sched_domain *sd, int cpu) > > > > > > used = READ_ONCE(rq->avg_rt.util_avg); > > > used += READ_ONCE(rq->avg_dl.util_avg); > > > + used += READ_ONCE(rq->avg_thermal.load_avg); > > > > Maybe a naive question - but can we add util_avg with load_avg without > > a conversion? I thought the 2 signals have different properties. > > Changelog of patch #1 explains, it's in that dense blob of text. > > But yes, you're quite right that that wants a comment here. Thanks for the pointer! A comment would be nice indeed. To make sure I got this correctly - it's because avg_thermal.load_avg represents delta_capacity which is already a 'converted' form of load. So this makes avg_thermal.load_avg a util_avg really. Correct? If I managed to get it right somehow. It'd be nice if we can do inverse conversion on delta_capacity so that avg_thermal.{load_avg, util_avg} meaning is consistent across the board. But I don't feel strongly about it if this gets documented properly. Thanks -- Qais Yousef