From nobody Fri Sep 12 15:53:56 2025 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 034CCC636D4 for ; Thu, 9 Feb 2023 07:14:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229978AbjBIHOx (ORCPT ); Thu, 9 Feb 2023 02:14:53 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48758 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229450AbjBIHOM (ORCPT ); Thu, 9 Feb 2023 02:14:12 -0500 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B899CA24A; Wed, 8 Feb 2023 23:14:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Content-Transfer-Encoding: MIME-Version:References:In-Reply-To:Message-Id:Date:Subject:Cc:To:From:Sender :Reply-To:Content-Type:Content-ID:Content-Description; bh=r8hE41Mkp5EbgMrksb3KX7Dta0yeg7VtidU0DErrk9U=; b=SSwLatKOiislYacsoo/Qi3JMlm b47ynisAwSrwGZYUASI66PxrUlyXGIC+yTFVomaUau58oZFIBo8jpLh1nKCHpGG1hzYaKwBa1fm5V MGzmE4oBMeEqrdn5s5zpFUd8r4fPoJzBc5Ip5AwXp99OeI1O5RmT/VlSbt0BYAksgp45OfAwRygNx i/pzyJ1nycNY+Xw/zZ/bZ4J0UyKubduraexKOGpFEp+Z26FQ29A6BoKJCASscbE4D41ElbfTj4DLm CFJF1BTGKjk9PTmvQUBILAJfIGvPULY2mO3cn6qHTxry4AKsGjQ6XNrMZ74qioxOvAb4QQpypQ9Ag iioQY5nQ==; Received: from [2601:1c2:980:9ec0::df2f] (helo=bombadil.infradead.org) by bombadil.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1pQ18F-000LPt-A5; Thu, 09 Feb 2023 07:14:11 +0000 From: Randy Dunlap To: linux-kernel@vger.kernel.org Cc: Randy Dunlap , Ingo Molnar , Peter Zijlstra , Juri Lelli , Vincent Guittot , Jonathan Corbet , linux-doc@vger.kernel.org, Mukesh Ojha Subject: [PATCH 16/24] Documentation: scheduler: correct spelling Date: Wed, 8 Feb 2023 23:13:52 -0800 Message-Id: <20230209071400.31476-17-rdunlap@infradead.org> X-Mailer: git-send-email 2.39.1 In-Reply-To: <20230209071400.31476-1-rdunlap@infradead.org> References: <20230209071400.31476-1-rdunlap@infradead.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" Correct spelling problems for Documentation/scheduler/ as reported by codespell. Signed-off-by: Randy Dunlap Cc: Ingo Molnar Cc: Peter Zijlstra Cc: Juri Lelli Cc: Vincent Guittot Cc: Jonathan Corbet Cc: linux-doc@vger.kernel.org Reviewed-by: Mukesh Ojha Acked-by: Vincent Guittot --- Documentation/scheduler/sched-bwc.rst | 2 +- Documentation/scheduler/sched-energy.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff -- a/Documentation/scheduler/sched-bwc.rst b/Documentation/scheduler/s= ched-bwc.rst --- a/Documentation/scheduler/sched-bwc.rst +++ b/Documentation/scheduler/sched-bwc.rst @@ -186,7 +186,7 @@ average usage, albeit over a longer time also limits the burst ability to no more than 1ms per cpu. This provides better more predictable user experience for highly threaded applications w= ith small quota limits on high core count machines. It also eliminates the -propensity to throttle these applications while simultanously using less t= han +propensity to throttle these applications while simultaneously using less = than quota amounts of cpu. Another way to say this, is that by allowing the unu= sed portion of a slice to remain valid across periods we have decreased the possibility of wastefully expiring quota on cpu-local silos that don't nee= d a diff -- a/Documentation/scheduler/sched-energy.rst b/Documentation/schedule= r/sched-energy.rst --- a/Documentation/scheduler/sched-energy.rst +++ b/Documentation/scheduler/sched-energy.rst @@ -82,7 +82,7 @@ through the arch_scale_cpu_capacity() ca The rest of platform knowledge used by EAS is directly read from the Energy Model (EM) framework. The EM of a platform is composed of a power cost tab= le per 'performance domain' in the system (see Documentation/power/energy-mod= el.rst -for futher details about performance domains). +for further details about performance domains). =20 The scheduler manages references to the EM objects in the topology code wh= en the scheduling domains are built, or re-built. For each root domain (rd), the @@ -281,7 +281,7 @@ mechanism called 'over-utilization'. From a general standpoint, the use-cases where EAS can help the most are t= hose involving a light/medium CPU utilization. Whenever long CPU-bound tasks are being run, they will require all of the available CPU capacity, and there = isn't -much that can be done by the scheduler to save energy without severly harm= ing +much that can be done by the scheduler to save energy without severely har= ming throughput. In order to avoid hurting performance with EAS, CPUs are flagg= ed as 'over-utilized' as soon as they are used at more than 80% of their compute capacity. As long as no CPUs are over-utilized in a root domain, load bala= ncing