From: Chen Ridong <chenridong@huaweicloud.com>
To: Sun Shaojie <sunshaojie@kylinos.cn>
Cc: cgroups@vger.kernel.org, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, longman@redhat.com,
mkoutny@suse.com, tj@kernel.org
Subject: Re: [PATCH -next] cpuset: treate root invalid trialcs as exclusive
Date: Mon, 17 Nov 2025 15:30:37 +0800 [thread overview]
Message-ID: <a46cd51e-e447-40f5-b2de-3067049ce491@huaweicloud.com> (raw)
In-Reply-To: <20251117065347.1052678-1-sunshaojie@kylinos.cn>
On 2025/11/17 14:53, Sun Shaojie wrote:
> On 2025/11/15 14:23, Chen Ridong wrote:
>> On 2025/11/17 12:35, Sun Shaojie wrote:
>>> Hi, Ridong,
>>>
>>> Maybe, this patch does not apply to the following cases:
>>> Step
>>> #1> echo "root" > A1/cpuset.cpus.partition
>>> #1> echo "0-1" > B1/cpuset.cpus
>>> #2> echo "1-2" > A1/cpuset.cpus.exclusive -> return error
>>> It should return success here.
>>>
>>> Please consider the following modification.
>>>
>>
>> If A1 will automatically change to a valid partition, I think it should return error.
>
> Hi, Ridong,
>
> A1 will not automatically change to a valid partition.
>
> Perhaps this example is more intuitive.
>
> For example:
>
> Before apply this patch:
> #1> echo "0-1" > B1/cpuset.cpus
> #2> echo "root" > A1/cpuset.cpus.partition -> A1's prstate is "root invalid"
> #3> echo "1-2" > A1/cpuset.cpus.exclusive
> Return success, and A1's prstate is "root invalid"
>
I did not apply your patch to test my patch. here are the results I obtained:
# cd /sys/fs/cgroup/
# mkdir A1
# mkdir B1
# echo 0-1 > B1/cpuset.cpus
# echo root > A1/cpuset.cpus.partition
# cat A1/cpuset.cpus.partition
root invalid (cpuset.cpus and cpuset.cpus.exclusive are empty)
# echo 1-2 > A1/cpuset.cpus
# cat A1/cpuset.cpus.partition
root
This differs from the results you provided.
Never mind, let's focus on whether the rule should be relaxed in your patch. Once that's resolved, I
can resubmit my patch. Let's set this patch aside for now.
Thanks.
--
Best regards,
Ridong
next prev parent reply other threads:[~2025-11-17 7:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 13:14 [PATCH v2] cpuset: relax the overlap check for cgroup-v2 Sun Shaojie
2025-11-13 14:57 ` Waiman Long
2025-11-13 17:07 ` Michal Koutný
2025-11-14 1:29 ` Chen Ridong
2025-11-14 16:14 ` Michal Koutný
2025-11-15 0:58 ` Chen Ridong
2025-11-14 0:50 ` Chen Ridong
2025-11-14 5:53 ` Sun Shaojie
2025-11-14 6:24 ` Sun Shaojie
2025-11-14 16:15 ` Michal Koutný
2025-11-15 2:01 ` Chen Ridong
2025-11-15 9:31 ` [PATCH -next] cpuset: treate root invalid trialcs as exclusive Chen Ridong
2025-11-16 14:08 ` [PATCH v2] cpuset: relax the overlap check for cgroup-v2 Sun Shaojie
2025-11-17 4:35 ` [PATCH -next] cpuset: treate root invalid trialcs as exclusive Sun Shaojie
2025-11-17 6:23 ` Chen Ridong
2025-11-17 6:53 ` Sun Shaojie
2025-11-17 7:30 ` Chen Ridong [this message]
2025-11-17 15:56 ` Waiman Long
2025-11-15 9:51 ` [PATCH v2] cpuset: relax the overlap check for cgroup-v2 Chen Ridong
2025-11-15 11:24 ` Sun Shaojie
2025-11-14 6:33 ` Sun Shaojie
2025-11-14 6:59 ` Chen Ridong
2025-11-15 6:02 ` Sun Shaojie
2025-11-15 7:41 ` Chen Ridong
2025-11-17 18:43 ` Waiman Long
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=a46cd51e-e447-40f5-b2de-3067049ce491@huaweicloud.com \
--to=chenridong@huaweicloud.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=sunshaojie@kylinos.cn \
--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