Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2727731pxb; Tue, 19 Jan 2021 04:48:04 -0800 (PST) X-Google-Smtp-Source: ABdhPJzckdr6W2JWXjm7B8RhZ6owMxR5i15Hsog+9HqtKvNKjbZfndv359k9oxamRpqawcVMyvTg X-Received: by 2002:a17:906:3b16:: with SMTP id g22mr2787660ejf.504.1611060484139; Tue, 19 Jan 2021 04:48:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611060484; cv=none; d=google.com; s=arc-20160816; b=ud70wkkflhNxFPQxyp+1FqjUMLIv7YKU8hdaYRW5OwkrOW66C9SCXmkKYlpTYYHv8g 1f9Bt2oYHsbwAOypqszBEgDzb3KhO0wJffxs/Qfn2wWtnsbdxV28ulK1Yluafarseevu MI1ghwOsgKbKWx02BqeXhoX2c7vFZU33UNJfaMauEm+OkcjYjCogm4b0qhoh8lCNwvim VS2eGE2j8NVooafvRGZzkXJxaUp1UPppV+++r0/ZJYF7RBOnIr0Hqc/HmVxdy1jopXox Enhe71ZEPlXBFGZLCykeiOtjx7TcjTYNktSn2rQ9RDo4lK4k86CL3UCDpHiX/1EwWf0n G2mg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:user-agent :references:in-reply-to:subject:cc:to:from; bh=BcaULGwAkFF5V7UxvQrkMhCxqB8vlIUEgRCUM5uqH0s=; b=PzA+FHGa+2OOAjo80hHAk8v2FCBK+1z6PmYRgdHN8mck8QdPemKjtxbspw5IF4LtvL nvnosWWxQKMgqtSSjJgtsM8bsuIiertjhwxfntJp486OzXhVn19FdQ3BRRzXTTWJactI hr1S3xi+eYLepH8j4J/dXWhVFQku1uoVTXThcqUsjM2wP6dvw5ilrEKBehhnzJfQzFfj 9f5odoZ6ufjDsjSRUoXJZWdJjiHQT2ZDb7mz/RXP4DtogytpaNyRuR1UZqBlTaY4qftQ CaPjgBuX7RVqik6OLQBpBbevDOfHa7nc+XiTCe33kOqjFuMRNgVC7SjE2gWHsHn2lkGG DV9A== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d7si8823458edx.507.2021.01.19.04.47.41; Tue, 19 Jan 2021 04:48:04 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2393073AbhASMcZ (ORCPT + 99 others); Tue, 19 Jan 2021 07:32:25 -0500 Received: from foss.arm.com ([217.140.110.172]:54870 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404319AbhASMZa (ORCPT ); Tue, 19 Jan 2021 07:25:30 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 31A2A1396; Tue, 19 Jan 2021 04:24:44 -0800 (PST) Received: from e113632-lin (e113632-lin.cambridge.arm.com [10.1.194.46]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 322033F719; Tue, 19 Jan 2021 04:24:43 -0800 (PST) From: Valentin Schneider To: Qais Yousef , "Peter Zijlstra \(Intel\)" , Dietmar Eggemann , Vincent Guittot Cc: linux-kernel@vger.kernel.org, Morten Rasmussen , Qais Yousef Subject: Re: [PATCH] sched/eas: Don't update misfit status if the task is pinned In-Reply-To: <20210119120755.2425264-1-qais.yousef@arm.com> References: <20210119120755.2425264-1-qais.yousef@arm.com> User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/26.3 (x86_64-pc-linux-gnu) Date: Tue, 19 Jan 2021 12:24:38 +0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Nit: Topic should probably be sched/fair - not many other than us loonies talk about EAS, and misfit stuff doesn't require an energy model, only CPU capacity asymmetry. On 19/01/21 12:07, Qais Yousef wrote: > If the task is pinned to a cpu, setting the misfit status means that > we'll unnecessarily continuously attempt to migrate the task but fail. > > This continuous failure will cause the balance_interval to increase to > a high value, and eventually cause unnecessary significant delays in > balancing the system when real imbalance happens. > > Caught while testing uclamp where rt-app calibration loop was pinned to > cpu 0, shortly after which we spawn another task with high util_clamp > value. The task was failing to migrate after over 40ms of runtime due to > balance_interval unnecessary expanded to a very high value from the > calibration loop. > > Not done here, but it could be useful to extend the check for pinning to > verify that the affinity of the task has a cpu that fits. We could end > up in a similar situation otherwise. > > Fixes: 3b1baa6496e6 ("sched/fair: Add 'group_misfit_task' load-balance type") > Signed-off-by: Qais Yousef Acked-by: Valentin Schneider Thanks! > --- > kernel/sched/fair.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c > index 197a51473e0c..9379a481dd8c 100644 > --- a/kernel/sched/fair.c > +++ b/kernel/sched/fair.c > @@ -4060,7 +4060,7 @@ static inline void update_misfit_status(struct task_struct *p, struct rq *rq) > if (!static_branch_unlikely(&sched_asym_cpucapacity)) > return; > > - if (!p) { > + if (!p || p->nr_cpus_allowed == 1) { > rq->misfit_task_load = 0; > return; > } > -- > 2.25.1