Received: by 10.192.165.156 with SMTP id m28csp881624imm; Wed, 11 Apr 2018 08:41:21 -0700 (PDT) X-Google-Smtp-Source: AIpwx48dsF5T0nhOu48KwzKuJDfLGshQn1eH4tEBMjVbDa1Qsk1cBM5RYPDB+s+6s0AYI3+FzenK X-Received: by 10.98.14.215 with SMTP id 84mr4456353pfo.168.1523461281850; Wed, 11 Apr 2018 08:41:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523461281; cv=none; d=google.com; s=arc-20160816; b=WRM21dWx2QN/rUzRl3U/nWNnEMrdpbfemW+8gtPIUo5gSNclZMnxt/bywpdo1fbKYW ff4lVR6yvw4fBBCCUXWgDpOfVPl9yEELtlR7S2dn2UGC99Qw6IeHgxg70J4VczPTul0m JEOTJNrH2It0PBP8fDTzrKn6r5urpIzKwe/QYJI/0HVf5XP/kclBkzhz0uVmvg2TpZ5u 5OQybr/kByzQjnwaxbnDXfqSbC2hBL5+xMiXbTcN5Z7R9tbuAreX4cnK5bUAHN7sPAVv YA7wB3rUCCr9qyMdh3Tx1dz4Awwk5m8gQ0W4KM+bM0p65/YQ5rTaLhWK5WlQeMSZaAaT w1yw== 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:dkim-signature:arc-authentication-results; bh=3SzyKXcMsPrl33GlcSOierHGwiZllv6Kt9N6o96sIkY=; b=hlBHMwy7UFJNXN0dJt4+5lYTo520g3/FEGIkGBqoujIqxsA78k9zmYajf3eQvsTHS4 qr5NBoTMoQKQgry3dJGHOAMIhBfM4lKuj4hjwERSuN1/6RGo+R367AKN/DcAvx3atFd3 d9nWT/NG+UA6VYWTNWBlJ2bXDneUBDGfbKWXNgH24o/H+FxBLNE2SMgoEirxhnZKPqxs 6l5wnNuT5c9yj72Qd0eGUOLXaVaXEW/xFC9LKUbWNm0EqZHW0OvxvoxtwLbP/QRRuSTm +lxEoYPzzp9vZuEoaF4VH4xiF566M73CaXiZT6qFhqDSHwaj/TVlPDxjSWA4kAB7ziha AN9w== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=lL6KfTkX; 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 v1-v6si1167060ply.711.2018.04.11.08.40.45; Wed, 11 Apr 2018 08:41:21 -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; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=lL6KfTkX; 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 S1753296AbeDKPhW (ORCPT + 99 others); Wed, 11 Apr 2018 11:37:22 -0400 Received: from merlin.infradead.org ([205.233.59.134]:48512 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752211AbeDKPhV (ORCPT ); Wed, 11 Apr 2018 11:37:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=3SzyKXcMsPrl33GlcSOierHGwiZllv6Kt9N6o96sIkY=; b=lL6KfTkXQEEfWwJ4kX7usCzsF l1wKjZgfFn2je4xfgoz73YkDk7a4GJ5N1DeMHDUbNMyBo+6X6Bnr826rsWonHFIM9dS2LJB0CjtkI pYeUy0/6W3Z91flAzfSn2eMsRceTzoR76LuXarWwfsE8kw09ukZJ3mLGRC/xYzMd93IPsR0yR9aKP Bvh9xb1hXIX+4w6JVS4uhIhbV3M03T3qOR+sTsCm2y14ufBUwZI4whhhz0nDAdm1wn4LS04rtawHe S43u3Rtr1OMJbJD596j2T2uO9Sa9fz0MttpY3kfvKqSP1ibnhlewu9ELcXnm6sy8KgSCoKWXEeo71 HbWZauh8A==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1f6Ho8-0006WK-9Q; Wed, 11 Apr 2018 15:37:12 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id AC0FF202A4A09; Wed, 11 Apr 2018 17:37:10 +0200 (CEST) Date: Wed, 11 Apr 2018 17:37:10 +0200 From: Peter Zijlstra To: Vincent Guittot Cc: Patrick Bellasi , linux-kernel , "open list:THERMAL" , Ingo Molnar , "Rafael J . Wysocki" , Viresh Kumar , Juri Lelli , Joel Fernandes , Steve Muckle , Dietmar Eggemann , Morten Rasmussen Subject: Re: [PATCH] sched/fair: schedutil: update only with all info available Message-ID: <20180411153710.GN4082@hirez.programming.kicks-ass.net> References: <20180406172835.20078-1-patrick.bellasi@arm.com> <20180410110412.GG14248@e110439-lin> <20180411151450.GK4043@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 11, 2018 at 05:29:01PM +0200, Vincent Guittot wrote: > On 11 April 2018 at 17:14, Peter Zijlstra wrote: > > On Tue, Apr 10, 2018 at 12:04:12PM +0100, Patrick Bellasi wrote: > >> On 09-Apr 10:51, Vincent Guittot wrote: > > > >> > Peter, > >> > what was your goal with adding the condition "if > >> > (rq->cfs.h_nr_running)" for the aggragation of CFS utilization > >> > >> The original intent was to get rid of sched class flags, used to track > >> which class has tasks runnable from within schedutil. The reason was > >> to solve some misalignment between scheduler class status and > >> schedutil status. > >> > >> The solution, initially suggested by Viresh, and finally proposed by > >> Peter was to exploit RQ knowledges directly from within schedutil. > >> > >> The problem is that now schedutil updated depends on two information: > >> utilization changes and number of RT and CFS runnable tasks. > >> > >> Thus, using cfs_rq::h_nr_running is not the problem... it's actually > >> part of a much more clean solution of the code we used to have. > >> > >> The problem, IMO is that we now depend on other information which > >> needs to be in sync before calling schedutil... and the patch I > >> proposed is meant to make it less likely that all the information > >> required are not aligned (also in the future). > > > > Specifically, the h_nr_running test was get rid of > > > > if (delta_ns > TICK_NSEC) { > > j_sg_cpu->iowait_boost = 0; > > j_sg_cpu->iowait_boost_pending = false; > > - j_sg_cpu->util_cfs = 0; > > > > ^^^^^^^^^^^^^^^^^^^^^^^ that.. > > > > - if (j_sg_cpu->util_dl == 0) > > - continue; > > } > > > > > > because that felt rather arbitrary. > > yes I agree. > > With the patch that updates blocked idle load, we should not have the > problem of blocked utilization anymore and get rid of the code above > and h_nr_running test Yes, these patches predate those, but indeed, now that we age the blocked load consistently it should no longer be required. Of course, you still have that weird regression report against those patches... :-)