Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 37B3FC636CC for ; Tue, 7 Feb 2023 09:45:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231205AbjBGJpu (ORCPT ); Tue, 7 Feb 2023 04:45:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51382 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230194AbjBGJpq (ORCPT ); Tue, 7 Feb 2023 04:45:46 -0500 Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 051B34224 for ; Tue, 7 Feb 2023 01:45:45 -0800 (PST) Received: by mail-pj1-x1034.google.com with SMTP id rm7-20020a17090b3ec700b0022c05558d22so14265234pjb.5 for ; Tue, 07 Feb 2023 01:45:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hnZlAZxHv1YnVbpbrT2tzh16DXY0Ol+anmyHp4u03I8=; b=gEfG/cotxT9+9lNJ56FTlASJsKmakQqxTRv8hHlkLi/r/QBJvSN9dyH5lGEwEksazl UAlJhz6kG4P0D6a8jePW49UquC6Z4vXG/t1gl29qBmzsj5/Ab2ZqhpRhu8oVv0p8q+Xj EJ4ef5lqSx6WN0ENsfHSdtvBFo+QECcn4AmEfs8dMcB5TFhmwVqNKkxzDXCn5Uhf2iWa Nr8lD4OejWoHvOlWEE40YIKW7VjQLLbg6yiDGDud+c/WB1SCgo2p0GIWarriFWGGJ+fe fRWBf4fOK2ZmoWcZHOj4EaZp+K2x1qLsvmdhvbb+1y8/lwMMMCdhwWNlwaCHa/Li1Oyo TUfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hnZlAZxHv1YnVbpbrT2tzh16DXY0Ol+anmyHp4u03I8=; b=X17VI7me6TOG4+90Lz5c/kOY+tJVEY4DzBB8wm5I2v7R06oaHDEioPAscV4eMti5aZ 18jl1hc7WREZB01Q1soUiMTfM64OSPYXeGq5roxZVa0OnPp1NRA88wjURUTzHTKxv9T3 mlidiF+Zh2tGc/NGErTXKufGvZaaBFbiH13vDPiGynFvdd7P3h0wDldV9hhE6gfAAFPI 7sWW0hZ3LcRRaLYK53jz9sQL85n9o1lfrWNB8DjI/c9SxPM4eBee/82KAcuv4ya9/SX5 9Te6PF3UI2XOh0T0aombxKRgSUqYQdxhhx8EuRiZFZeLdu8n66WK2HKO+X3fzPPhG6i8 YBIw== X-Gm-Message-State: AO0yUKU3KvJQeBC5DEqodjnBcJVKxhA+M0AEgGX5c5MCugtlbPlpIXBe zF9Ar4uDHpNhsjUn/k0b4tOFdF4kMOExTnanX51sDA== X-Google-Smtp-Source: AK7set+v3kIUBwyNqSSWhcarIEZq+PcamRs5udiY44jaYM9Qlo4/6+ZyuZZ+8kIqQGYVZ6/u/KmA56sa0ImT+iJBOEY= X-Received: by 2002:a17:90a:7006:b0:230:7ea2:1a04 with SMTP id f6-20020a17090a700600b002307ea21a04mr667866pjk.112.1675763144402; Tue, 07 Feb 2023 01:45:44 -0800 (PST) MIME-Version: 1.0 References: <20230205224318.2035646-1-qyousef@layalina.io> <20230205224318.2035646-2-qyousef@layalina.io> In-Reply-To: <20230205224318.2035646-2-qyousef@layalina.io> From: Vincent Guittot Date: Tue, 7 Feb 2023 10:45:33 +0100 Message-ID: Subject: Re: [PATCH v2 1/3] sched/uclamp: Set max_spare_cap_cpu even if max_spare_cap is 0 To: Qais Yousef Cc: Ingo Molnar , Peter Zijlstra , Dietmar Eggemann , linux-kernel@vger.kernel.org, Lukasz Luba , Wei Wang , Xuewen Yan , Hank , Jonathan JMChen Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 5 Feb 2023 at 23:43, Qais Yousef wrote: > > When uclamp_max is being used, the util of the task could be higher than > the spare capacity of the CPU, but due to uclamp_max value we force fit > it there. > > The way the condition for checking for max_spare_cap in > find_energy_efficient_cpu() was constructed; it ignored any CPU that has > its spare_cap less than or _equal_ to max_spare_cap. Since we initialize > max_spare_cap to 0; this lead to never setting max_spare_cap_cpu and > hence ending up never performing compute_energy() for this cluster and > missing an opportunity for a better energy efficient placement to honour > uclamp_max setting. > > max_spare_cap = 0; > cpu_cap = capacity_of(cpu) - task_util(p); // 0 if task_util(p) is high > > ... > > util_fits_cpu(...); // will return true if uclamp_max forces it to fit > > ... > > // this logic will fail to update max_spare_cap_cpu if cpu_cap is 0 > if (cpu_cap > max_spare_cap) { > max_spare_cap = cpu_cap; > max_spare_cap_cpu = cpu; > } > > prev_spare_cap suffers from a similar problem. > > Fix the logic by converting the variables into long and treating -1 > value as 'not populated' instead of 0 which is a viable and correct > spare capacity value. > > Fixes: 1d42509e475c ("sched/fair: Make EAS wakeup placement consider uclamp restrictions") > Signed-off-by: Qais Yousef (Google) > --- > kernel/sched/fair.c | 9 ++++----- > 1 file changed, 4 insertions(+), 5 deletions(-) > > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c > index c6c8e7f52935..7a21ee74139f 100644 > --- a/kernel/sched/fair.c > +++ b/kernel/sched/fair.c > @@ -7382,11 +7382,10 @@ static int find_energy_efficient_cpu(struct task_struct *p, int prev_cpu) > for (; pd; pd = pd->next) { > unsigned long util_min = p_util_min, util_max = p_util_max; > unsigned long cpu_cap, cpu_thermal_cap, util; > - unsigned long cur_delta, max_spare_cap = 0; > + long prev_spare_cap = -1, max_spare_cap = -1; > unsigned long rq_util_min, rq_util_max; > - unsigned long prev_spare_cap = 0; > + unsigned long cur_delta, base_energy; > int max_spare_cap_cpu = -1; > - unsigned long base_energy; > int fits, max_fits = -1; > > cpumask_and(cpus, perf_domain_span(pd), cpu_online_mask); > @@ -7461,7 +7460,7 @@ static int find_energy_efficient_cpu(struct task_struct *p, int prev_cpu) > } > } > > - if (max_spare_cap_cpu < 0 && prev_spare_cap == 0) > + if (max_spare_cap_cpu < 0 && prev_spare_cap < 0) > continue; > > eenv_pd_busy_time(&eenv, cpus, p); > @@ -7469,7 +7468,7 @@ static int find_energy_efficient_cpu(struct task_struct *p, int prev_cpu) > base_energy = compute_energy(&eenv, pd, cpus, p, -1); > > /* Evaluate the energy impact of using prev_cpu. */ > - if (prev_spare_cap > 0) { > + if (prev_spare_cap > -1) { > prev_delta = compute_energy(&eenv, pd, cpus, p, > prev_cpu); > /* CPU utilization has changed */ I think that you also need the change below to make sure that the signed comparison will be used. I have quickly checked the assembly code for aarch64 and your patch keeps using unsigned comparison (b.ls) ((fits == max_fits) && (cpu_cap > max_spare_cap))) { ffff8000080e4c94: f94067e0 ldr x0, [sp, #200] ffff8000080e4c98: eb00003f cmp x1, x0 ffff8000080e4c9c: 54ff98a9 b.ls ffff8000080e3fb0 // b.plast Whereas the change below make it to use the signed version (b.le) ((fits == max_fits) && ((long)cpu_cap > max_spare_cap))) { ffff8000080e4c94: f94067e0 ldr x0, [sp, #200] ffff8000080e4c98: eb00003f cmp x1, x0 ffff8000080e4c9c: 54ff98ad b.le ffff8000080e3fb0 -- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -7522,7 +7522,7 @@ static int find_energy_efficient_cpu(struct task_struct *p, int prev_cpu) prev_spare_cap = cpu_cap; prev_fits = fits; } else if ((fits > max_fits) || - ((fits == max_fits) && (cpu_cap > max_spare_cap))) { + ((fits == max_fits) && ((long)cpu_cap > max_spare_cap))) { /* * Find the CPU with the maximum spare capacity * among the remaining CPUs in the performance > -- > 2.25.1 >