Received: by 10.223.176.5 with SMTP id f5csp1155995wra; Tue, 6 Feb 2018 13:47:53 -0800 (PST) X-Google-Smtp-Source: AH8x225WRY/cWSEtcHDdT+hSEUSc1diafQg2wkqK2aH8b7WyaCeENmz+QT12OfrzPu6RkBhWb8cq X-Received: by 2002:a17:902:24a2:: with SMTP id w31-v6mr3690902pla.262.1517953673464; Tue, 06 Feb 2018 13:47:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517953673; cv=none; d=google.com; s=arc-20160816; b=Fcz9o/hWu/25qZV3UGAGOzfylxK7O40YvFYAAW0Iog7tir1qcX48mw5VWMDvYoHcZ/ 1Mn2WcTWS27ANyC13LGeiHkaKFU3suEBmGvS5k/DI+t11JnfkEYlUzjcKWPV4xbKYxJ0 wBwyebbelBz0z4iwnAVBxt9DOoKKILhiv2HkIqJZIKKNC0/TOGtTE72jpOOlxlIZUgEW XMkzVtuN/Kx7WNdgJgabnIT4XxFiWttKt/G67XGvuWVVv5gXqU+7+0zF4n7/DS4S2OoX tGbtNSRzFv1MshFdRuV9JtCDhR/di0lPZmDwSIIsopbMP3OsSEcq9Upzq9D+rvtw4/EF qF4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=X+0p6y2uM8n2GzIXxLsbiiTEuXQmpgLqJp6cxrNDHBY=; b=J/nB7LnqrJHgYwu9nzA4GDHMtb2vWxoiF5Xkd5V+y3Q9AFHnVQfOstTMBhR/Reawl/ qoqrf3zn9GZTipYqwxtt2+417jG32zINZABMlYXA5MELw3mqNQ5iMnOWvEm83XRXYQi3 rgSbb5pQTemeaH1fP3qwof5U4R837v7fPvSbOI/21DBnzThIxIdCHKg3wFvo0Q4uRysF QfZBgm0535dMnL/Trs8widnGMqZv3IAixcCjTiaz7FR1N22MK8DZtbEZw3Dui5NTUxwB 9LPrIYnrd6CaihUA626yFvBdvlOlMJEYajT3mftJifwsCX7l7lhTfQNLE43D3mSnFjmA cMhA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Fs47Xn/J; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e19si1899797pfl.212.2018.02.06.13.47.38; Tue, 06 Feb 2018 13:47:53 -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; dkim=pass header.i=@linaro.org header.s=google header.b=Fs47Xn/J; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753153AbeBFVrA (ORCPT + 99 others); Tue, 6 Feb 2018 16:47:00 -0500 Received: from mail-io0-f193.google.com ([209.85.223.193]:43716 "EHLO mail-io0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752968AbeBFVq7 (ORCPT ); Tue, 6 Feb 2018 16:46:59 -0500 Received: by mail-io0-f193.google.com with SMTP id 72so4091011iom.10 for ; Tue, 06 Feb 2018 13:46:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=X+0p6y2uM8n2GzIXxLsbiiTEuXQmpgLqJp6cxrNDHBY=; b=Fs47Xn/JJf5+oW37kPyNOjuRBkTaKsqOFwdYtoFUQgjR4K8yN/d7ZDqGq5p7whRHOs 7MoXOfMaLdn6xYDSJUH7wuFOOHufCpAdd/vSmJsmhfulD5rxxAMePE8YbLwgscc3nrUs x1voL1C3ZiA1OuA7llEc7vgkOkdiV2/h+q4ac= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=X+0p6y2uM8n2GzIXxLsbiiTEuXQmpgLqJp6cxrNDHBY=; b=YCac/oLqG/xEAUqsm07O/owqet3YCPcwnOOC4goKHTwjs3EOnTIqbhPBv+TcQBLuOu UuKKUpE+uNN7AfmVwlu3BSufbwwQBbwUFK4cf84BInw6ZY4nbpAAKKcF6uzwa8rzYjTg fKTiQ5u2cQXRmUX/V3vv4JqnyUKlSRyVJ1FdQbQd7BxRlDLaIFSbtNxQql647HQMdow/ /4dI0k1rpwuZOIwpWyjOcWh/Dy8CzjtvmgbjBYYVHzIbPvAeSpmDT96ua6grG6l9Zpj6 vh9OOuTjeOvZ7QImOa2clLRZaJWN0YPJC07mnJKQPSMG4pZDCWP2vXrOENJvteGvObm4 eyhQ== X-Gm-Message-State: APf1xPB635G/os9gjOMgCrQvtkASohOrftQDYFvaKJVbcGaRlGWlPaYD cqDstIjt2XsfYqzobtf5Jm3nLsbSoeCLfutcgukHtQ== X-Received: by 10.107.178.195 with SMTP id b186mr5208046iof.9.1517953618700; Tue, 06 Feb 2018 13:46:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.50.198 with HTTP; Tue, 6 Feb 2018 13:46:37 -0800 (PST) In-Reply-To: <20180206212507.GO2249@hirez.programming.kicks-ass.net> References: <1517944987-343-1-git-send-email-vincent.guittot@linaro.org> <20180206212507.GO2249@hirez.programming.kicks-ass.net> From: Vincent Guittot Date: Tue, 6 Feb 2018 22:46:37 +0100 Message-ID: Subject: Re: [PATCH v2 0/3] Update blocked load To: Peter Zijlstra Cc: Ingo Molnar , linux-kernel , Valentin Schneider , Morten Rasmussen , Brendan Jackman , Dietmar Eggemann Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6 February 2018 at 22:25, Peter Zijlstra wrote: > On Tue, Feb 06, 2018 at 08:23:04PM +0100, Vincent Guittot wrote: >> This patchset applies on top of Peter's sched/esting branch minus the last 2 commit: >> 56eb46798b33 ("sched: Clean up nohz enter/exit") > > So what will update the blocked load after we wake from a total idle? > > I don't see anything here that would do that (yet?). The fast wake up path uses only idle state and runnable load average. The later is normally up to date and null ( thanks to the propagation of runnable) because of the fact that we were totally idle. For the other "slow" path, we need to update the utilization of the CPUs when we use them (and the load as well even if we don't use it). This will be part of another patch as the overhead need to be evaluated That should be enough to take the right decision at wake up from a long total idle state Then for a complete update of the load metric, we can either wait for the next tick or kick an ilb at wake up (what you don't like).