Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp866530pxb; Tue, 1 Feb 2022 12:03:54 -0800 (PST) X-Google-Smtp-Source: ABdhPJyLzh0cD1SC0wdOuj/Wqx0onIxPpKJGN1zGo3cpNLhbIPIZCItG9Y5N9L22AJ/Bi2pxWP0M X-Received: by 2002:a05:6402:5110:: with SMTP id m16mr27412028edd.325.1643745834111; Tue, 01 Feb 2022 12:03:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643745834; cv=none; d=google.com; s=arc-20160816; b=FefPdlpiOm43qmCJNjrTnaTIbQMFSLSgmWKvWJcS+s1MIsrGJRY8IJ/P9n8/CMQXPq F+4a0PUvkiVRoaByOHMat3c7C+X4V+Y2jgM+oab+Hz1SqHgJM4RqHzluYImLmItJpyoW 2DQQqoNiKUOxmkt8ngGAH7970iXwmL6jCNNUwMeibdUCPabfSM8h13t4J0X7xSOvFNDq wBKjl7HCiV9k0KPYPvAxfdOqQ8PNIoHa4FLqFj7VVV745FqE2fMNakOu9AnTdh9xLIIh vKvhUvhrQN5D4VzH404FSbe3Am7xNNFjr2zrg5ra1IH+U8/XufG6Su4R7alZMDA2XLJ/ 4JHQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=8v7JLX8EUrLYxoLseSuQQMsv4oCDhfaLxYfigQzjT5g=; b=DmaMec4LkVaB0SZxhEGosMgx8XoM3YY3BEIlJ2etIFcmx0AGBVLW/umbgQgye/lMBa 5skP1YLgcA+JZicHs1Z3kePEiKjpjBq97Y7RtDcW7E9QRTG2TiVoZvjCLYhqgseE1TUW 6MMUlr2rMAWctM4adCCex+pin4gacshL3GmecxdEGH7aVS6WIzTDRe78AyrxYKyVnJWv asrnL3efaWsYETI1d85ct35hTQ0H5O972qLnI1Bqhkdg/y9A21BQRxtZZtM28uieM0Y1 7b+hJTNCpK0igmpkqIjjy2eWKPi+EQdWD5iI9KjX8b/5zBPUdGr6WrwpXplFGlGlLxoN C/SA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=18Qr1qrS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h22si9509561edt.145.2022.02.01.12.03.23; Tue, 01 Feb 2022 12:03:54 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=18Qr1qrS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1359425AbiAaLQu (ORCPT + 99 others); Mon, 31 Jan 2022 06:16:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44372 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1377169AbiAaLJp (ORCPT ); Mon, 31 Jan 2022 06:09:45 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 88691C0604CA; Mon, 31 Jan 2022 03:06:28 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 2794460FB5; Mon, 31 Jan 2022 11:06:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EA66BC340E8; Mon, 31 Jan 2022 11:06:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1643627187; bh=Nc46HbOlscxH1ZoeqPE08D0tvHM0jh6dbN/WgavK4V0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=18Qr1qrSSg2IJjB7PRReUVX8Q85srXRZWUZINWKYyT2n1ByOHOJstErZ5Z9aEIYy9 MLJiL+TZqXdjFDvzORVc3FBd/LjAzRx2YHtPEVARu8PaVD0ecG2EbPn7cWTBiU/9r+ 2aM8sZm3vfXRtyabPrUaQd8UmaxVmrgC2BVJsr50= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Rick Yiu , Vincent Guittot , "Peter Zijlstra (Intel)" , Dietmar Eggemann , Sachin Sant , Sasha Levin Subject: [PATCH 5.10 072/100] sched/pelt: Relax the sync of util_sum with util_avg Date: Mon, 31 Jan 2022 11:56:33 +0100 Message-Id: <20220131105222.848675855@linuxfoundation.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20220131105220.424085452@linuxfoundation.org> References: <20220131105220.424085452@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Vincent Guittot [ Upstream commit 98b0d890220d45418cfbc5157b3382e6da5a12ab ] Rick reported performance regressions in bugzilla because of cpu frequency being lower than before: https://bugzilla.kernel.org/show_bug.cgi?id=215045 He bisected the problem to: commit 1c35b07e6d39 ("sched/fair: Ensure _sum and _avg values stay consistent") This commit forces util_sum to be synced with the new util_avg after removing the contribution of a task and before the next periodic sync. By doing so util_sum is rounded to its lower bound and might lost up to LOAD_AVG_MAX-1 of accumulated contribution which has not yet been reflected in util_avg. Instead of always setting util_sum to the low bound of util_avg, which can significantly lower the utilization of root cfs_rq after propagating the change down into the hierarchy, we revert the change of util_sum and propagate the difference. In addition, we also check that cfs's util_sum always stays above the lower bound for a given util_avg as it has been observed that sched_entity's util_sum is sometimes above cfs one. Fixes: 1c35b07e6d39 ("sched/fair: Ensure _sum and _avg values stay consistent") Reported-by: Rick Yiu Signed-off-by: Vincent Guittot Signed-off-by: Peter Zijlstra (Intel) Reviewed-by: Dietmar Eggemann Tested-by: Sachin Sant Link: https://lkml.kernel.org/r/20220111134659.24961-2-vincent.guittot@linaro.org Signed-off-by: Sasha Levin --- kernel/sched/fair.c | 16 +++++++++++++--- kernel/sched/pelt.h | 4 +++- 2 files changed, 16 insertions(+), 4 deletions(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 8d2f238fdd2ac..acd9833b8ec22 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -3379,7 +3379,6 @@ void set_task_rq_fair(struct sched_entity *se, se->avg.last_update_time = n_last_update_time; } - /* * When on migration a sched_entity joins/leaves the PELT hierarchy, we need to * propagate its contribution. The key to this propagation is the invariant @@ -3447,7 +3446,6 @@ void set_task_rq_fair(struct sched_entity *se, * XXX: only do this for the part of runnable > running ? * */ - static inline void update_tg_cfs_util(struct cfs_rq *cfs_rq, struct sched_entity *se, struct cfs_rq *gcfs_rq) { @@ -3676,7 +3674,19 @@ update_cfs_rq_load_avg(u64 now, struct cfs_rq *cfs_rq) r = removed_util; sub_positive(&sa->util_avg, r); - sa->util_sum = sa->util_avg * divider; + sub_positive(&sa->util_sum, r * divider); + /* + * Because of rounding, se->util_sum might ends up being +1 more than + * cfs->util_sum. Although this is not a problem by itself, detaching + * a lot of tasks with the rounding problem between 2 updates of + * util_avg (~1ms) can make cfs->util_sum becoming null whereas + * cfs_util_avg is not. + * Check that util_sum is still above its lower bound for the new + * util_avg. Given that period_contrib might have moved since the last + * sync, we are only sure that util_sum must be above or equal to + * util_avg * minimum possible divider + */ + sa->util_sum = max_t(u32, sa->util_sum, sa->util_avg * PELT_MIN_DIVIDER); r = removed_runnable; sub_positive(&sa->runnable_avg, r); diff --git a/kernel/sched/pelt.h b/kernel/sched/pelt.h index 0b9aeebb9c325..45bf08e22207c 100644 --- a/kernel/sched/pelt.h +++ b/kernel/sched/pelt.h @@ -37,9 +37,11 @@ update_irq_load_avg(struct rq *rq, u64 running) } #endif +#define PELT_MIN_DIVIDER (LOAD_AVG_MAX - 1024) + static inline u32 get_pelt_divider(struct sched_avg *avg) { - return LOAD_AVG_MAX - 1024 + avg->period_contrib; + return PELT_MIN_DIVIDER + avg->period_contrib; } static inline void cfs_se_util_change(struct sched_avg *avg) -- 2.34.1