Received: by 2002:a5d:9c59:0:0:0:0:0 with SMTP id 25csp1672536iof; Tue, 7 Jun 2022 09:32:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzup6Zx9//Dpa3kIU6D4STqlFpbrU0srhFcgoNil46LtofB1dxhtiR/6Sspx5+1Giu+vRxu X-Received: by 2002:a17:902:d2c9:b0:167:1195:3a41 with SMTP id n9-20020a170902d2c900b0016711953a41mr24193271plc.126.1654619554312; Tue, 07 Jun 2022 09:32:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654619554; cv=none; d=google.com; s=arc-20160816; b=AgkNoIa3fm+XwEaYUESM9sIfy+5w0jKFNJPw7kuGWLFDHPrVZUS/1DymtgGKgKkqVk 5FyUjpnxogbuPZakZOfMsDlv0oIg4/WYhjq2x92y0KeNgD6CZy22u77I1sMizt2IInlf nxkqd6F7aeoTkhbIlMLfzMxmXsRTxPSDojf24GkWl2bcZ+v41GGHw/4K8+Myi05IjtUU j0a222K45zHy0YpKxs/D3Obvth7m8lPENrLzGDyClveLSFaeur4LFGS2G0CSf2TuZN+K J7oyhVFXvueTRWA8AXaCLGUpX7QYP9w2K8MluBwNZnDzDvaTufO2Qs9FqjNqyhWaxOLz B8SA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:from:subject :mime-version:message-id:date:dkim-signature; bh=bC3KeebU1bUh3sAba0smjA6aSdf5vl469Ak2N5dfab0=; b=0s2hG6sI4I7u8ft3LX2fDXKAI95131Tg5V+ApDxgPVWeBWg8pfpNdUhZIlhrC4kjVS 8kyy5ne85QrJtiHNwgDNtJ5oxF+WoFlpxLsjZVjJPAeV9HzIXnjJEBcNLwiodiPOyik4 LGndIEXwrrypo570h1rbB/rkZlA918ihf+rxDOH07TINpg48HqAGS3RR98pmFkgDS2V+ c51zBh0RuzfHwZuIg66ldE6ZE4ylqxaNCSFz2OtsBk43v3EBeHRE75R17Nv10ZRIWpX9 atrXbBTI8+WFmVWZ72mOMXZ+GwNpF673IA6OD8tyN/CFWfVCYaKMbhc3cK0+VWK03Sxh 0Wtw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=jwG5pE6o; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id n4-20020a622704000000b005184296cd5bsi22258145pfn.344.2022.06.07.09.32.18; Tue, 07 Jun 2022 09:32:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=jwG5pE6o; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243920AbiFGMgp (ORCPT + 99 others); Tue, 7 Jun 2022 08:36:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54904 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243881AbiFGMgh (ORCPT ); Tue, 7 Jun 2022 08:36:37 -0400 Received: from mail-wr1-x449.google.com (mail-wr1-x449.google.com [IPv6:2a00:1450:4864:20::449]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DB3E7D4A21 for ; Tue, 7 Jun 2022 05:36:19 -0700 (PDT) Received: by mail-wr1-x449.google.com with SMTP id t2-20020adfe442000000b002108370e7a3so3843450wrm.3 for ; Tue, 07 Jun 2022 05:36:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:message-id:mime-version:subject:from:to:cc :content-transfer-encoding; bh=bC3KeebU1bUh3sAba0smjA6aSdf5vl469Ak2N5dfab0=; b=jwG5pE6oXtSACk3sG+8fNVJK4ecF5TAWmcre88xqhMcK3uWYWWp1lFwuzlIMHP5NDr 858ItZvcTlMKXgdtFSMPma0lCGDI5+f3T8Ue/ibxfNney6Z+GxuqagxKK5OeVridXNPL kECN9VJaqDB7revmRJ0haR7dc62XkhrCJOWNCd4T3LT4+eXuKDE8JrjgLVDZZ+VHgwQK GBsEpJaTXYLrjzEy722snyZggY9pGK642R8k17LHSv1B2dvF6aBO7il1V/Z7jnjapqrX BiwhCLU84aY7lZfujL4hSvp8MkWFz9X9keVZXSgPjBaY3N5wN/Vewa6hcHgkjc/P6CYd 6r8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:message-id:mime-version:subject:from:to:cc :content-transfer-encoding; bh=bC3KeebU1bUh3sAba0smjA6aSdf5vl469Ak2N5dfab0=; b=5kicJuzkpzc4A8HC9km06or7Qcz6HeFyMIHhOXue4xVSugLpCmf7Cok4fa1QuK05FX yAy0p8HPJaBrioDV6QbXiGyoFvy0YA3xb0fmfP/pSBvuGLiHEi0TpzZTjIv9No9xFasD AJojM9kLNXD8f9C0R/Q4FMUKm3scDy/MK4yIa6dbqbSNhEtIyNSbPfdcNlLkZa0BE0qE MLvC1HwG9Pkbx0zPHSmsFpoDEDtsKWAZ1YckzJtdVOeusikl+3uA2j0s2doSl2rY5f11 uWoHtUrp922n9tWP6LY6PRohRuWWzJiktN/Xb9K0OA6hmiPFXROvWWd6UnJxHMkrUu9d xbZQ== X-Gm-Message-State: AOAM531rQ24Dry78KCbeZt35LeOIwCKCiKUXlG/AQ4xppHxx5k4jI1kG v+SE8cu+B05rBTfgQW7WxZq9affMCZ+6iWPK X-Received: from vdonnefort.c.googlers.com ([fda3:e722:ac3:cc00:28:9cb1:c0a8:2eea]) (user=vdonnefort job=sendgmr) by 2002:a5d:64c7:0:b0:216:5021:687f with SMTP id f7-20020a5d64c7000000b002165021687fmr17691682wri.295.1654605378185; Tue, 07 Jun 2022 05:36:18 -0700 (PDT) Date: Tue, 7 Jun 2022 13:32:47 +0100 Message-Id: <20220607123254.565579-1-vdonnefort@google.com> Mime-Version: 1.0 X-Mailer: git-send-email 2.36.1.255.ge46751e96f-goog Subject: [PATCH v10 0/7] feec() energy margin removal From: Vincent Donnefort To: peterz@infradead.org, mingo@redhat.com, vincent.guittot@linaro.org Cc: linux-kernel@vger.kernel.org, dietmar.eggemann@arm.com, morten.rasmussen@arm.com, chris.redpath@arm.com, qperret@google.com, tao.zhou@linux.dev, kernel-team@android.com, vdonnefort@google.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-9.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Here's a new version of the patch-set to get rid of the energy margin in feec(). Many thanks to all for the insightful comments I got. find_energy_efficient() (feec()) will migrate a task to save energy only if it saves at least 6% of the total energy consumed by the system. This conservative approach is a problem on a system where a lot of small tasks create a huge load on the overall: very few of them will be allowed to migrate to a smaller CPU, wasting a lot of energy. Instead of trying to determine yet another margin, let's try to remove it. The first elements of this patch-set are various fixes and improvement that stabilizes task_util and ensures energy comparison fairness across all CPUs of the topology. Only once those fixed, we can completely remove the margin and let feec() aggressively place task and save energy. This has been validated by two different ways: First using LISA's eas_behaviour test suite. This is composed of a set of scenario and verify if the task placement is optimum. No failure have been observed and it also improved some tests such as Ramp-Down (as the placement is now more energy oriented) and *ThreeSmall (as no bouncing between clusters happen anymore). * Hikey960: 100% PASSED * DB-845C: 100% PASSED * RB5: 100% PASSED Second, using an Android benchmark: PCMark2 on a Pixel4, with a lot of backports to have a scheduler as close as we can from mainline. +------------+-----------------+-----------------+ | Test | Perf | Energy [1] | +------------+-----------------+-----------------+ | Web2 | -0.3% pval 0.03 | -1.8% pval 0.00 | | Video2 | -0.3% pval 0.13 | -5.6% pval 0.00 | | Photo2 [2] | -3.8% pval 0.00 | -1% pval 0.00 | | Writing2 | 0% pval 0.13 | -1% pval 0.00 | | Data2 | 0% pval 0.8 | -0.43 pval 0.00 | +------------+-----------------+-----------------+ The margin removal let the kernel make the best use of the Energy Model, tasks are more likely to be placed where they fit and this saves a substantial amount of energy, while having a limited impact on performances. [1]=C2=A0This is an energy estimation based on the CPU activity and the Ene= rgy Model for this device. "All models are wrong but some are useful"; yes, this is an imperfect estimation that doesn't take into account some idle states and shared power rails. Nonetheless this is based on the information the kernel has during runtime and it proves the scheduler can take better decisions based solely on those data. [2] This is the only performance impact observed. The debugging of this test showed no issue with task placement. The better score was solely due to some critical threads held on better performing CPUs. If a thread needs a higher capacity CPU, the placement must result from a user input (with e.g. uclamp min) instead of being artificially held on less efficient CPUs by feec(). Notice also, the experiment didn't use the Android only latency_sensitive feature which would hide this problem on a real-life device. v9 -> v10: - Cosmetic changes for comments and commit messages. (Dietmar/Vincent G.) - Renaming timestamp variables. (Dietmar) - Fix for empty mask in feec(). (Dietmar) - Collect Reviewed-by tags. v8 -> v9: - PELT migration decay: Fix barriers to prevent overestimation. (Vincent G.) - PELT migration decay: Fix CONFIG_GROUP_SCHED=3Dn build. - Various readbility improvements. (Dietmar) - Collect Reviewed-by tags. v7 -> v8: - PELT migration decay: Refine estimation computation. (vincent G.) - PELT migration decay: Do not apply estimation if load_avg is decayed (Tao) - PELT migration decay: throttled_pelt_idle update ordering for the update_blocked_load case. (vincent G.) v6 -> v7: - PELT migration decay: Add missing clock_pelt_idle updates. - PELT migration decay: Fix PELT scaling delta for CONFIG_CFS_BANDWIDTH. v4 -> v5: - PELT migration decay: timestamp only at idle time (Vincent G.) - PELT migration decay: split timestamp values (enter_idle / clock_pelt_idle) (Vincent G.) v3 -> v4: - Minor cosmetic changes (Dietmar) v2 -> v3: - feec(): introduce energy_env struct (Dietmar) - PELT migration decay: Only apply when src CPU is idle (Vincent G.) - PELT migration decay: Do not apply when cfs_rq is throttled - PELT migration decay: Snapshot the lag at cfs_rq's level v1 -> v2: - Fix PELT migration last_update_time (previously root cfs_rq's). - Add Dietmar's patches to refactor feec()'s CPU loop. - feec(): renaming busy time functions get_{pd,tsk}_busy_time() - feec(): pd_cap computation in the first for_each_cpu loop. - feec(): create get_pd_max_util() function (previously within compute_energy()) - feec(): rename base_energy_pd to base_energy. Dietmar Eggemann (3): sched, drivers: Remove max param from effective_cpu_util()/sched_cpu_util() sched/fair: Rename select_idle_mask to select_rq_mask sched/fair: Use the same cpumask per-PD throughout find_energy_efficient_cpu() Vincent Donnefort (4): sched/fair: Provide u64 read for 32-bits arch helper sched/fair: Decay task PELT values during wakeup migration sched/fair: Remove task_util from effective utilization in feec() sched/fair: Remove the energy margin in feec() drivers/powercap/dtpm_cpu.c | 33 +-- drivers/thermal/cpufreq_cooling.c | 6 +- include/linux/sched.h | 2 +- kernel/sched/core.c | 15 +- kernel/sched/cpufreq_schedutil.c | 5 +- kernel/sched/fair.c | 470 +++++++++++++++++++----------- kernel/sched/pelt.h | 40 ++- kernel/sched/sched.h | 53 +++- 8 files changed, 400 insertions(+), 224 deletions(-) --=20 2.36.1.255.ge46751e96f-goog