Message ID | 5fc042e1d3c5d63b9367a1e1587dcf6b548087ff.1689071768.git.geert+renesas@glider.be |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:a6b2:0:b0:3e4:2afc:c1 with SMTP id c18csp386751vqm; Tue, 11 Jul 2023 03:54:52 -0700 (PDT) X-Google-Smtp-Source: APBJJlG4FQsKKCpbhw5F8S5YYC8BH1X/IKnya6+eDE+BHaXRZDPTHp+jOB/bCRK7z1nDaleASYb4 X-Received: by 2002:a2e:80c4:0:b0:2b6:9b2e:e352 with SMTP id r4-20020a2e80c4000000b002b69b2ee352mr13332808ljg.9.1689072892504; Tue, 11 Jul 2023 03:54:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689072892; cv=none; d=google.com; s=arc-20160816; b=Xrg0jfnJtmyCmK9uSOwrbLmnvpGN6dl+GjFk4XMjDCBHOyWldqcko1nn6sC2Bg5aLl 70mGEPK+oQDkZV+zyveH/UUuEbxFKStvVWEG/sD6UWH2krsjQMgr7q6oZmTwMCDsaVvv s8nsBsLusRjDWuEDrRfT6F5LMK7BRmDs41y2nY4RPvFSfnS5c1vg/59cDRCOBQeUjrFA NfoYvjNrpv+yjVa3/9oAZfKuOIe3ZsJXnEBMuAE9E5w/hL/HsIYjj1b/zvbEmeKjZowR MRX6mwR+nmlxsDRkW/J9kdjx/1Np+kBcAoxrzS7QR0mqJyKEKXby59xDxo7DZJCOVRzr OKsg== 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 :message-id:date:subject:cc:to:from; bh=NDlzrr3EKkT/GfW0s4UzUAnXnHR1Joelu3Rhw+Sklc0=; fh=4zxEUP33ha1CiFp9sjNCL07cxACFLU/j8GGoqF5CgMM=; b=z9I2k1YfPvY57y6dHGiBry75dv3IiLLo0jwb5l2TY5cjKJZvfQSoWPz1NdsbmOS3+q Q6pgVnWpIxc1lXWCoNdNMtfMh7CHNVzvCbotcAaI8jeIFBfyLznDqH9Ro7KZb5rPXU5a UJpywq2A6Npn+U3uoSHl6vJA0k+ukTInrP4LXDjthSphR0+PoruzTQj83jznl6p5tLg7 jYSCDDVrEOsHtLA3xJCxDyfGQmkI/banc7XOJ1N3qjWrKLiR0JCwlLIGMYKGdgNTsqfl Ev0vELZDZgQ9byjt9Ud2N/KiGh5t70KxOFdIzQtsqTWyAvFBsOeRpz1/pvNNZ75UqUDZ 9wbg== ARC-Authentication-Results: i=1; mx.google.com; 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 Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u5-20020a170906950500b0099251942e1bsi1852602ejx.82.2023.07.11.03.54.28; Tue, 11 Jul 2023 03:54:52 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230490AbjGKKib (ORCPT <rfc822;gnulinuxfreebsd@gmail.com> + 99 others); Tue, 11 Jul 2023 06:38:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57682 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229742AbjGKKi2 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 11 Jul 2023 06:38:28 -0400 Received: from albert.telenet-ops.be (albert.telenet-ops.be [IPv6:2a02:1800:110:4::f00:1a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 218111A2 for <linux-kernel@vger.kernel.org>; Tue, 11 Jul 2023 03:38:26 -0700 (PDT) Received: from ramsan.of.borg ([IPv6:2a02:1810:ac12:ed40:2b42:575f:41f:104f]) by albert.telenet-ops.be with bizsmtp id KmeP2A0024w94eT06mePsZ; Tue, 11 Jul 2023 12:38:25 +0200 Received: from rox.of.borg ([192.168.97.57]) by ramsan.of.borg with esmtp (Exim 4.95) (envelope-from <geert@linux-m68k.org>) id 1qJAl6-0017MR-5u; Tue, 11 Jul 2023 12:38:23 +0200 Received: from geert by rox.of.borg with local (Exim 4.95) (envelope-from <geert@linux-m68k.org>) id 1qJAlC-00Clyk-VC; Tue, 11 Jul 2023 12:38:22 +0200 From: Geert Uytterhoeven <geert+renesas@glider.be> To: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>, Peter Zijlstra <peterz@infradead.org> Cc: linux-kernel@vger.kernel.org, Geert Uytterhoeven <geert+renesas@glider.be> Subject: [PATCH] workqueue: Fix cpu_intensive_thresh_us name in help text Date: Tue, 11 Jul 2023 12:38:20 +0200 Message-Id: <5fc042e1d3c5d63b9367a1e1587dcf6b548087ff.1689071768.git.geert+renesas@glider.be> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=no 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1771121297489636114 X-GMAIL-MSGID: 1771121297489636114 |
Series |
workqueue: Fix cpu_intensive_thresh_us name in help text
|
|
Commit Message
Geert Uytterhoeven
July 11, 2023, 10:38 a.m. UTC
There exists no parameter called "cpu_intensive_threshold_us".
The actual parameter name is "cpu_intensive_thresh_us".
Fixes: 6363845005202148 ("workqueue: Report work funcs that trigger automatic CPU_INTENSIVE mechanism")
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
On 7/11/23 03:38, Geert Uytterhoeven wrote: > There exists no parameter called "cpu_intensive_threshold_us". > The actual parameter name is "cpu_intensive_thresh_us". > > Fixes: 6363845005202148 ("workqueue: Report work funcs that trigger automatic CPU_INTENSIVE mechanism") > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Thanks. > --- > lib/Kconfig.debug | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index c8371502b4b2e678..5da00849edebafdd 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -1200,7 +1200,7 @@ config WQ_CPU_INTENSIVE_REPORT > help > Say Y here to enable reporting of concurrency-managed per-cpu work > items that hog CPUs for longer than > - workqueue.cpu_intensive_threshold_us. Workqueue automatically > + workqueue.cpu_intensive_thresh_us. Workqueue automatically > detects and excludes them from concurrency management to prevent > them from stalling other per-cpu work items. Occassional > triggering may not necessarily indicate a problem. Repeated
On Tue, Jul 11, 2023 at 12:38:20PM +0200, Geert Uytterhoeven wrote: > There exists no parameter called "cpu_intensive_threshold_us". > The actual parameter name is "cpu_intensive_thresh_us". > > Fixes: 6363845005202148 ("workqueue: Report work funcs that trigger automatic CPU_INTENSIVE mechanism") > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > --- > lib/Kconfig.debug | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index c8371502b4b2e678..5da00849edebafdd 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -1200,7 +1200,7 @@ config WQ_CPU_INTENSIVE_REPORT > help > Say Y here to enable reporting of concurrency-managed per-cpu work > items that hog CPUs for longer than > - workqueue.cpu_intensive_threshold_us. Workqueue automatically > + workqueue.cpu_intensive_thresh_us. Workqueue automatically > detects and excludes them from concurrency management to prevent > them from stalling other per-cpu work items. Occassional > triggering may not necessarily indicate a problem. Repeated Applied to wq/for-6.5-fixes. Thanks.
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index c8371502b4b2e678..5da00849edebafdd 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -1200,7 +1200,7 @@ config WQ_CPU_INTENSIVE_REPORT help Say Y here to enable reporting of concurrency-managed per-cpu work items that hog CPUs for longer than - workqueue.cpu_intensive_threshold_us. Workqueue automatically + workqueue.cpu_intensive_thresh_us. Workqueue automatically detects and excludes them from concurrency management to prevent them from stalling other per-cpu work items. Occassional triggering may not necessarily indicate a problem. Repeated