From: Tejun Heo <tj@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueue: Fix cpu_intensive_thresh_us name in help text
Date: Tue, 11 Jul 2023 11:33:39 -1000 [thread overview]
Message-ID: <ZK3Ks3gkO7XykGYY@slm.duckdns.org> (raw)
In-Reply-To: <5fc042e1d3c5d63b9367a1e1587dcf6b548087ff.1689071768.git.geert+renesas@glider.be>
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.
--
tejun
prev parent reply other threads:[~2023-07-11 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 10:38 Geert Uytterhoeven
2023-07-11 14:50 ` Randy Dunlap
2023-07-11 21:33 ` Tejun Heo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZK3Ks3gkO7XykGYY@slm.duckdns.org \
--to=tj@kernel.org \
--cc=geert+renesas@glider.be \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®