From: Randy Dunlap <rdunlap@infradead.org>
To: Audra Mitchell <audra@redhat.com>, corbet@lwn.net
Cc: tj@kernel.org, jiangshanlai@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, raquini@redhat.com, aros@gmx.com
Subject: Re: [PATCH] Documentation/core-api: Update events_freezable_power references.
Date: Wed, 3 Apr 2024 13:27:50 -0700 [thread overview]
Message-ID: <9a079670-bbed-4f5d-9ef6-876bb1d82d39@infradead.org> (raw)
In-Reply-To: <20240403180022.16248-1-audra@redhat.com>
On 4/3/24 11:00 AM, Audra Mitchell wrote:
> Due to commit 8318d6a6362f ("workqueue: Shorten
> events_freezable_power_efficient name") we now have some stale
> references in the workqeueue documentation, so updating those
> references accordingly.
>
> Signed-off-by: Audra Mitchell <audra@redhat.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/core-api/workqueue.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/core-api/workqueue.rst b/Documentation/core-api/workqueue.rst
> index ed73c612174d..bcc370c876be 100644
> --- a/Documentation/core-api/workqueue.rst
> +++ b/Documentation/core-api/workqueue.rst
> @@ -671,7 +671,7 @@ configuration, worker pools and how workqueues map to the pools: ::
> events_unbound unbound 9 9 10 10 8
> events_freezable percpu 0 2 4 6
> events_power_efficient percpu 0 2 4 6
> - events_freezable_power_ percpu 0 2 4 6
> + events_freezable_pwr_ef percpu 0 2 4 6
> rcu_gp percpu 0 2 4 6
> rcu_par_gp percpu 0 2 4 6
> slub_flushwq percpu 0 2 4 6
> @@ -694,7 +694,7 @@ Use tools/workqueue/wq_monitor.py to monitor workqueue operations: ::
> events_unbound 38306 0 0.1 - 7 - -
> events_freezable 0 0 0.0 0 0 - -
> events_power_efficient 29598 0 0.2 0 0 - -
> - events_freezable_power_ 10 0 0.0 0 0 - -
> + events_freezable_pwr_ef 10 0 0.0 0 0 - -
> sock_diag_events 0 0 0.0 0 0 - -
>
> total infl CPUtime CPUhog CMW/RPR mayday rescued
> @@ -704,7 +704,7 @@ Use tools/workqueue/wq_monitor.py to monitor workqueue operations: ::
> events_unbound 38322 0 0.1 - 7 - -
> events_freezable 0 0 0.0 0 0 - -
> events_power_efficient 29603 0 0.2 0 0 - -
> - events_freezable_power_ 10 0 0.0 0 0 - -
> + events_freezable_pwr_ef 10 0 0.0 0 0 - -
> sock_diag_events 0 0 0.0 0 0 - -
>
> ...
--
#Randy
prev parent reply other threads:[~2024-04-03 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 18:00 Audra Mitchell
2024-04-03 18:45 ` Tejun Heo
2024-04-03 20:27 ` Randy Dunlap [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=9a079670-bbed-4f5d-9ef6-876bb1d82d39@infradead.org \
--to=rdunlap@infradead.org \
--cc=aros@gmx.com \
--cc=audra@redhat.com \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raquini@redhat.com \
--cc=tj@kernel.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®