From: Randy Dunlap <rdunlap@infradead.org>
To: Xuewen Yan <xuewen.yan@unisoc.com>,
tj@kernel.org, jiangshanlai@gmail.com, corbet@lwn.net
Cc: paulmck@kernel.org, peterz@infradead.org, yanjiewtw@gmail.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
ke.wang@unisoc.com, xuewen.yan94@gmail.com
Subject: Re: [PATCH] workqueue: Control the frequency of intensive warning through cmdline
Date: Mon, 19 Feb 2024 08:00:52 -0800 [thread overview]
Message-ID: <8cae5358-d1f3-4e86-950f-bb72a940ed3f@infradead.org> (raw)
In-Reply-To: <20240219074634.2039-1-xuewen.yan@unisoc.com>
On 2/18/24 23:46, Xuewen Yan wrote:
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 31b3a25680d0..599fc59fcf70 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -7225,6 +7225,15 @@
> threshold repeatedly. They are likely good
> candidates for using WQ_UNBOUND workqueues instead.
>
> + workqueue.cpu_intensive_warning_per_count=
workqueue.cpu_intensive_warning_per_count=<uint>
or
<integer>
> + If CONFIG_WQ_CPU_INTENSIVE_REPORT is set, the kernel
> + will report the work functions which violate the
> + intensive_threshold_us repeatedly. In order to prevent
> + the kernel log from being printed too frequently.
frequently,
control
> + Control the frequency.
> +
> + Default, it will print one warning per 4 times.
By default,
> +
--
#Randy
next prev parent reply other threads:[~2024-02-19 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 7:46 Xuewen Yan
2024-02-19 16:00 ` Randy Dunlap [this message]
2024-02-20 16:46 ` Tejun Heo
2024-02-21 2:01 ` Xuewen Yan
2024-02-21 5:44 ` Tejun Heo
2024-02-21 11:00 ` Xuewen Yan
2024-02-21 17:44 ` Tejun Heo
2024-02-22 1:52 ` Xuewen Yan
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=8cae5358-d1f3-4e86-950f-bb72a940ed3f@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=ke.wang@unisoc.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=xuewen.yan94@gmail.com \
--cc=xuewen.yan@unisoc.com \
--cc=yanjiewtw@gmail.com \
/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®