Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp619782ybv; Wed, 19 Feb 2020 06:04:20 -0800 (PST) X-Google-Smtp-Source: APXvYqyFNkYJbYgQr0qQnWGlDEwuvKj0Q7W7RtlbGPXQtr/cywYz7HpJ/6KbFWMGUw/7hnOhOSRj X-Received: by 2002:aca:c4c4:: with SMTP id u187mr4457036oif.120.1582121060057; Wed, 19 Feb 2020 06:04:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582121060; cv=none; d=google.com; s=arc-20160816; b=qdxJMi1AfY/Ea8+RUPSWQMCkI/ON8CPPO0qTqdn0xytYZ1ONmD1jXnd4xdExCc/i6P 8TIa45zGFXpCb6Gf7WMn/D5fQdAuAEkJT7okmKSGEknXGDhhXZW1nXo3A5TZUPVQ01BP McaK5BBsHkUTOOj8SrfSajcyuBYTOhV3IwdJKasjNLZz0OEHno75dAGYYEMgn8u6cpAx 8bkSF0uZBLWP88QY8V9VDFuSgB/UtQFRxg6JNTRNqZSHUSYyjeII31LMvSOS5YW/1He5 i2wgs3hvZZ2JcAhGVSCmpszR6aaq64J1nkqb0vd814ogKbI2AgoHAym7TPJenFyKJ8By GNww== 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=JqXsYd6KZO6Sv/n+Pa3FVK0kKiMjif2pZ+0dILFXpYI=; b=sTH70uT6U804LiyExyvNmVGxEn4T23iK/Er1cRhOYIK1B9Ek+joggFEBHEHfNgCkFL FZPchelNunmCn2PVKkiThxwKjjzwX1u/Mp99EptlDgvuf4h6EkVkkcmw3/GLei9Gts2c c6A2dZyEM00rpoV4uXuC438yrh5kkTTkRkB9Nf8OCPl+jV/Qz0+4y5E4GkVo9Q45mo6e kzc5EW31MajRN4O5GPvyx5adR5rrAMM6OnjBOgNUpxLl2l9N/tnpcxpUQEAEoCG0Jjdf iv8Cn139cOfHeGkiMZINsIjtu7oAkbCvrOAvvw1vK6sAytThSN+yknldEGiDRAadp7mO xL9A== 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 d23si9804682oij.270.2020.02.19.06.04.00; Wed, 19 Feb 2020 06:04:20 -0800 (PST) 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 S1727933AbgBSOCY (ORCPT + 99 others); Wed, 19 Feb 2020 09:02:24 -0500 Received: from outbound-smtp16.blacknight.com ([46.22.139.233]:39152 "EHLO outbound-smtp16.blacknight.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727756AbgBSOCV (ORCPT ); Wed, 19 Feb 2020 09:02:21 -0500 Received: from mail.blacknight.com (pemlinmail01.blacknight.ie [81.17.254.10]) by outbound-smtp16.blacknight.com (Postfix) with ESMTPS id 508D31C1B30 for ; Wed, 19 Feb 2020 14:02:19 +0000 (GMT) Received: (qmail 3146 invoked from network); 19 Feb 2020 14:02:19 -0000 Received: from unknown (HELO techsingularity.net) (mgorman@techsingularity.net@[84.203.18.57]) by 81.17.254.9 with ESMTPSA (AES256-SHA encrypted, authenticated); 19 Feb 2020 14:02:19 -0000 Date: Wed, 19 Feb 2020 14:02:17 +0000 From: Mel Gorman To: Vincent Guittot Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com, dietmar.eggemann@arm.com, rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de, linux-kernel@vger.kernel.org, pauld@redhat.com, parth@linux.ibm.com, valentin.schneider@arm.com, hdanton@sina.com Subject: Re: [PATCH v3 4/5] sched/pelt: Add a new runnable average signal Message-ID: <20200219140216.GP3466@techsingularity.net> References: <20200214152729.6059-5-vincent.guittot@linaro.org> <20200219125513.8953-1-vincent.guittot@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20200219125513.8953-1-vincent.guittot@linaro.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 19, 2020 at 01:55:13PM +0100, Vincent Guittot wrote: > Now that runnable_load_avg has been removed, we can replace it by a new > signal that will highlight the runnable pressure on a cfs_rq. This signal > track the waiting time of tasks on rq and can help to better define the > state of rqs. > > At now, only util_avg is used to define the state of a rq: > A rq with more that around 80% of utilization and more than 1 tasks is > considered as overloaded. > > But the util_avg signal of a rq can become temporaly low after that a task > migrated onto another rq which can bias the classification of the rq. > > When tasks compete for the same rq, their runnable average signal will be > higher than util_avg as it will include the waiting time and we can use > this signal to better classify cfs_rqs. > > The new runnable_avg will track the runnable time of a task which simply > adds the waiting time to the running time. The runnable _avg of cfs_rq > will be the /Sum of se's runnable_avg and the runnable_avg of group entity > will follow the one of the rq similarly to util_avg. > > Tested-by: Valentin Schneider > Signed-off-by: Vincent Guittot Thanks. Picked up and included in "Reconcile NUMA balancing decisions with the load balancer v4". The only change I made to your patches was move the reintroduction of cpu_runnable to the patch that requires it to avoid a build warning. -- Mel Gorman SUSE Labs