From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, Josh Don <joshdon@google.com>,
Tejun Heo <tj@kernel.org>, Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>
Cc: Linux CGroups <cgroups@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Attreyee M <tintinm2017@gmail.com>
Subject: Re: [PATCH] cgroup: Fix documentation for cpu.idle
Date: Sat, 2 Dec 2023 08:25:52 +0700 [thread overview]
Message-ID: <53769b00-086e-4913-a0d1-606322d2ced5@gmail.com> (raw)
In-Reply-To: <87fs0meyzw.fsf@meer.lwn.net>
On 12/1/23 22:14, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
>
>> On Thu, Nov 30, 2023 at 04:52:03PM -0800, Josh Don wrote:
>>> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
>>> index 3f85254f3cef..9debf02bcb39 100644
>>> --- a/Documentation/admin-guide/cgroup-v2.rst
>>> +++ b/Documentation/admin-guide/cgroup-v2.rst
>>> + cpu.idle
>>> + A read-write single value file which exists on non-root cgroups.
>>> + The default is 0.
>>> +
>>> + This is the cgroup analog of the per-task SCHED_IDLE sched policy.
>> "... cgroup analogy to ..."
>>> + Setting this value to a 1 will make the scheduling policy of the
>
> Bagas, please stop this (again). The original wording is better than
> your suggested "improvement".
>
OK, withdrawn!
And then,
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Sorry for inconvenience.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-12-02 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 0:52 [PATCH] cgroup: Fix documentation for cpu.idle Josh Don
2023-12-01 5:48 ` Bagas Sanjaya
2023-12-01 15:14 ` Jonathan Corbet
2023-12-02 1:25 ` Bagas Sanjaya [this message]
2023-12-01 16:49 ` Tejun Heo
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=53769b00-086e-4913-a0d1-606322d2ced5@gmail.com \
--to=bagasdotme@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=joshdon@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=tintinm2017@gmail.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