mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Guopeng Zhang <guopeng.zhang@linux.dev>,
	Ridong Chen <ridong.chen@linux.dev>
Cc: "Tejun Heo" <tj@kernel.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Guopeng Zhang" <zhangguopeng@kylinos.cn>
Subject: Re: [PATCH v3 0/2] docs: cgroup-v2: Correct cpuset CPU descriptions
Date: Tue, 22 Sep 2026 19:30:46 -0400	[thread overview]
Message-ID: <9fadb6a1-df92-4c8f-96f3-f5fdf43e68d4@redhat.com> (raw)
In-Reply-To: <20260922092034.68840-1-guopeng.zhang@linux.dev>

On 9/22/26 5:20 AM, Guopeng Zhang wrote:
> From: Guopeng Zhang <zhangguopeng@kylinos.cn>
>
> The cpuset interface documentation says cpuset.cpus.isolated is empty
> unless an isolated partition exists, omitting CPUs isolated at boot with
> isolcpus=domain. Its cpuset.cpus.effective description also assumes CPUs
> come from the immediate parent and are normally a subset of
> cpuset.cpus, which is not always true for valid non-root partition roots.
>
> Update both descriptions to match the existing behavior.
>
> Changes since v2:
> - Update the valid partition root example to show that an offline CPU
>    can remain in cpuset.cpus.exclusive.effective while being excluded
>    from cpuset.cpus.effective.
> - Add the Reviewed-by tag to patch 2.
> - Patch 1 is unchanged.
>
> Guopeng Zhang (2):
>    docs: cgroup-v2: Describe boot-isolated CPUs in cpuset.cpus.isolated
>    docs: cgroup-v2: Describe effective CPUs of partition roots
>
>   Documentation/admin-guide/cgroup-v2.rst | 62 ++++++++++++++++++++-----
>   1 file changed, 51 insertions(+), 11 deletions(-)

For the patch series,

Reviewed-by: Waiman Long <longman@redhat.com>


  parent reply	other threads:[~2026-09-22 23:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  9:20 Guopeng Zhang
2026-09-22  9:20 ` [PATCH v3 1/2] docs: cgroup-v2: Describe boot-isolated CPUs in cpuset.cpus.isolated Guopeng Zhang
2026-09-22  9:20 ` [PATCH v3 2/2] docs: cgroup-v2: Describe effective CPUs of partition roots Guopeng Zhang
2026-09-22 23:30 ` Waiman Long [this message]
2026-09-23 18:37 ` [PATCH v3 0/2] docs: cgroup-v2: Correct cpuset CPU descriptions 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=9fadb6a1-df92-4c8f-96f3-f5fdf43e68d4@redhat.com \
    --to=longman@redhat.com \
    --cc=cgroups@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=guopeng.zhang@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=ridong.chen@linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=tj@kernel.org \
    --cc=zhangguopeng@kylinos.cn \
    /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®