Received: by 10.223.148.5 with SMTP id 5csp7220657wrq; Thu, 18 Jan 2018 02:33:43 -0800 (PST) X-Google-Smtp-Source: ACJfBov/apNXiw/IBlfL8EWbxCBtA4Zp98ulIVf9FSOOwgNLnRiY1EuzclLTChn19yar6TyiDTp1 X-Received: by 10.98.53.195 with SMTP id c186mr41830454pfa.115.1516271623563; Thu, 18 Jan 2018 02:33:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516271623; cv=none; d=google.com; s=arc-20160816; b=FeGh8lDfDFQonPMLWQpD0dYdt4pT3ThNehLPYzHYvu90XryhnCVzaVHtHdf1z4cLL2 SU4Ch/XuDM586zHpcW8lLDLgVoFOE6eESF/U9Gq4sH6Pz6atc8spAcE6CnGDXcDeDGF6 t5pLNGy93iNIOrSTEIxWH89FHHvVdXgFNZljMe50yUiBASG2HuxDXEvEMj1FMGEqQEhm GfotRXIQq2JB8HYX+RsvbIMTzq3ZCY04pJYkPbJKfgLEhTMUpu0I/lFeXNMQlMmCaXFI K8LZTzZ4J2tuMkuRuJEBA5yLN/uDJYxeraiX4VNL2C7w2vD4c/oMFWSQlQBczBxtvmNi 4wrQ== 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:arc-authentication-results; bh=Bx0uHc5RVOoWsjOoCfBmNI0xO5hG28PJJRlcjO5bPl4=; b=NNzgBMw+WRK3d7k0EhNuBEr64UoMgez1102HFUV+8kvMBjB0tq7sTTJZyq6M60fdjG qN9NAJS1VEyRU4vQ1pmY4g1lct1/gsg6rq9Ndly4nk7764h9viGkV2FspXOygxG3L1Tf GKdMQN+Ek7voFNVcAgbd4olpBAGDD24LuVN3dyCWGXSFPCmZx4T0wR36nOFc2jfYA+r/ WozXJQVDbhGei1c/hbmHYBuKce/QU+f9w3Oypbr4xW7WJuC01xZRT/aldNrkaMEqE/B8 rOVhuU8I2p9HHMBt2MEj6lvRKd5+i3a/d0Pc1u9ipggKw+rywmhhEjgRah/vf8qcZ7QW /8bw== 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 n7si6408976plp.140.2018.01.18.02.33.29; Thu, 18 Jan 2018 02:33:43 -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 S1755857AbeARKck (ORCPT + 99 others); Thu, 18 Jan 2018 05:32:40 -0500 Received: from foss.arm.com ([217.140.101.70]:52964 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754962AbeARKci (ORCPT ); Thu, 18 Jan 2018 05:32:38 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 612621529; Thu, 18 Jan 2018 02:32:38 -0800 (PST) Received: from e105550-lin.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 0ABB73F557; Thu, 18 Jan 2018 02:32:36 -0800 (PST) Date: Thu, 18 Jan 2018 10:32:34 +0000 From: Morten Rasmussen To: Peter Zijlstra Cc: Vincent Guittot , Ingo Molnar , linux-kernel , Brendan Jackman , Dietmar Eggemann , Morten Rasmussen Subject: Re: [RFC PATCH 2/5] sched: Add NOHZ_STATS_KICK Message-ID: <20180118103234.GC28799@e105550-lin.cambridge.arm.com> References: <20171222075934.f6yenvcb2zkf2ysd@hirez.programming.kicks-ass.net> <20171222082915.4lcb7xyyooqyjpia@hirez.programming.kicks-ass.net> <20171222091221.ow5vn3ydx3hj4nht@hirez.programming.kicks-ass.net> <20171222185629.lysjebfifgdwvvhu@hirez.programming.kicks-ass.net> <20171222204247.kyc6ugyyu3ei7zhs@hirez.programming.kicks-ass.net> <20180102154457.GB28799@e105550-lin.cambridge.arm.com> <20180115094317.GN6176@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180115094317.GN6176@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 15, 2018 at 10:43:18AM +0100, Peter Zijlstra wrote: > On Tue, Jan 02, 2018 at 03:44:57PM +0000, Morten Rasmussen wrote: > > > Vincent already proposed, why can't we just modify Brendan's > > CPU_NEWLY_IDLE proposal to do a stats update from idle_balance() every > > 32ms regardless of whether we need to load-balance? > > I think that code is there, no? > > Subject: sched: Update blocked load from NEWIDLE The mechanics are there, but I think the problem is that the idle_balance() bails out before we get to it in some cases. If we only have a few small periodic tasks running rd->overload won't be set and idle_balance() returns before doing anything. We would need some sort of check to see if a PELT update is due and make sure it happens, even if idle_balance() has nothing to do.