From: Jonathan Corbet <corbet@lwn.net>
To: Phil Auld <pauld@redhat.com>, linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation/sysctl: Add timer_migration to kernel.rst
Date: Tue, 14 Jan 2025 10:08:13 -0700 [thread overview]
Message-ID: <877c6x9vcy.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250114140301.141147-1-pauld@redhat.com>
Phil Auld <pauld@redhat.com> writes:
> There is no mention of timer_migration in the docs. Add
> a short description.
>
> Signed-off-by: Phil Auld <pauld@redhat.com>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> ---
> Documentation/admin-guide/sysctl/kernel.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index b2b36d0c3094..e03691e2cf4a 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -1544,6 +1544,13 @@ constant ``FUTEX_TID_MASK`` (0x3fffffff).
> If a value outside of this range is written to ``threads-max`` an
> ``EINVAL`` error occurs.
>
> +timer_migration
> +===============
> +
> +When set, attempt to migrate timers away from idle cpus to allow them to remain
> +in low power states longer.
> +
> +Default is set.
When set to *what*? It will always be set to *some* value, right? So
we should really say what the specific values mean.
Thanks,
jon
next prev parent reply other threads:[~2025-01-14 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 14:03 [PATCH] Documentation/sysctl: Add timer_migration to kernel.rst Phil Auld
2025-01-14 17:08 ` Jonathan Corbet [this message]
2025-01-14 17:43 ` Phil Auld
2025-01-14 18:40 ` Jonathan Corbet
2025-01-14 19:04 ` Phil Auld
2025-01-14 19:50 ` Phil Auld
2025-01-14 19:56 ` Jonathan Corbet
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=877c6x9vcy.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pauld@redhat.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