From: Chen Ridong <chenridong@huaweicloud.com>
To: Waiman Long <llong@redhat.com>,
tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
lujialin4@huawei.com, chenridong@huawei.com
Subject: Re: [PATCH -next RFC 01/11] cpuset: move the root cpuset write check earlier
Date: Sat, 30 Aug 2025 09:11:20 +0800 [thread overview]
Message-ID: <4e662ffa-acc6-448c-bfc7-7b3d16b40341@huaweicloud.com> (raw)
In-Reply-To: <e02b9c35-c51e-45c0-a2ca-3d1f0492af23@redhat.com>
On 2025/8/30 3:21, Waiman Long wrote:
> On 8/28/25 8:56 AM, Chen Ridong wrote:
>> From: Chen Ridong <chenridong@huawei.com>
>>
>> The 'cpus' or 'mems' lists of the top_cpuset cannot be modified.
>> This check can be moved before acquiring any locks as a common code
>> block to improve efficiency and maintainability.
>>
>> Signed-off-by: Chen Ridong <chenridong@huawei.com>
>> ---
>> kernel/cgroup/cpuset.c | 22 +++++++++-------------
>> 1 file changed, 9 insertions(+), 13 deletions(-)
>>
>> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
>> index a78ccd11ce9b..7e6a40e361ea 100644
>> --- a/kernel/cgroup/cpuset.c
>> +++ b/kernel/cgroup/cpuset.c
>> @@ -337,6 +337,11 @@ static inline bool cpuset_v2(void)
>> cgroup_subsys_on_dfl(cpuset_cgrp_subsys);
>> }
>> +static inline bool cpuset_is_root(struct cpuset *cs)
>> +{
>> + return (cs == &top_cpuset);
>> +}
>> +
>> /*
>> * Cgroup v2 behavior is used on the "cpus" and "mems" control files when
>> * on default hierarchy or when the cpuset_v2_mode flag is set by mounting
>> @@ -2334,10 +2339,6 @@ static int update_cpumask(struct cpuset *cs, struct cpuset *trialcs,
>> bool force = false;
>> int old_prs = cs->partition_root_state;
>> - /* top_cpuset.cpus_allowed tracks cpu_active_mask; it's read-only */
>> - if (cs == &top_cpuset)
>> - return -EACCES;
>> -
>> /*
>> * An empty cpus_allowed is ok only if the cpuset has no tasks.
>> * Since cpulist_parse() fails on an empty mask, we special case
>> @@ -2783,15 +2784,6 @@ static int update_nodemask(struct cpuset *cs, struct cpuset *trialcs,
>> {
>> int retval;
>> - /*
>> - * top_cpuset.mems_allowed tracks node_stats[N_MEMORY];
>> - * it's read-only
>> - */
>> - if (cs == &top_cpuset) {
>> - retval = -EACCES;
>> - goto done;
>> - }
>> -
>> /*
>> * An empty mems_allowed is ok iff there are no tasks in the cpuset.
>> * Since nodelist_parse() fails on an empty mask, we special case
>> @@ -3257,6 +3249,10 @@ ssize_t cpuset_write_resmask(struct kernfs_open_file *of,
>> struct cpuset *trialcs;
>> int retval = -ENODEV;
>> + /* root is read-only */
>> + if (cpuset_is_root(cs))
>> + return -EACCES;
>> +
>> buf = strstrip(buf);
>> cpuset_full_lock();
>> if (!is_cpuset_online(cs))
>
> The (cs == &top_cpuset) check is pretty straight forward. So if the cpuset_is_root() helper is only
> used once, I don't think we need a new helper here.
>
> Cheers,
> Longman
Thanks you Longman,
There are several places where cs == &top_cpuset could be replaced with the helper function
cpuset_is_root. However, since this series focuses on refactoring the CPU settings, I did not make
those replacements. Would it be acceptable to submit a separate patch that introduces this helper?
--
Best regards,
Ridong
next prev parent reply other threads:[~2025-08-30 1:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 12:56 [PATCH -next RFC 00/11] Refactor cpus mask setting Chen Ridong
2025-08-28 12:56 ` [PATCH -next RFC 01/11] cpuset: move the root cpuset write check earlier Chen Ridong
2025-08-29 19:21 ` Waiman Long
2025-08-30 1:11 ` Chen Ridong [this message]
2025-08-28 12:56 ` [PATCH -next RFC 02/11] cpuset: remove unused assignment to trialcs->partition_root_state Chen Ridong
2025-08-28 12:56 ` [PATCH -next RFC 03/11] cpuset: change return type of is_partition_[in]valid to bool Chen Ridong
2025-08-28 12:56 ` [PATCH -next RFC 04/11] cpuset: Refactor exclusive CPU mask computation logic Chen Ridong
2025-08-28 12:56 ` [PATCH -next RFC 05/11] cpuset: refactor CPU mask buffer parsing logic Chen Ridong
2025-08-28 12:56 ` [PATCH -next RFC 06/11] cpuset: introduce cpus_excl_conflict and mems_excl_conflict helpers Chen Ridong
2025-08-29 19:29 ` Waiman Long
2025-08-30 1:27 ` Chen Ridong
2025-08-28 12:56 ` [PATCH -next RFC 07/11] cpuset: refactor out invalidate_cs_partition Chen Ridong
2025-08-29 19:56 ` Waiman Long
2025-08-30 1:33 ` Chen Ridong
2025-08-28 12:56 ` [PATCH -next RFC 08/11] cpuset: refactor acpus_validate_change Chen Ridong
2025-08-29 20:12 ` Waiman Long
2025-08-30 1:42 ` Chen Ridong
2025-08-28 12:56 ` [PATCH -next RFC 09/11] cpuset: refactor partition_cpus_change Chen Ridong
2025-08-29 20:32 ` Waiman Long
2025-08-30 2:01 ` Chen Ridong
2025-09-02 13:30 ` Waiman Long
2025-09-03 0:51 ` Chen Ridong
2025-08-28 12:56 ` [PATCH -next RFC 10/11] cpuset: use parse_cpulist for setting cpus.exclusive Chen Ridong
2025-08-28 12:56 ` [PATCH -next RFC 11/11] cpuset: use partition_cpus_change for setting exclusive cpus Chen Ridong
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=4e662ffa-acc6-448c-bfc7-7b3d16b40341@huaweicloud.com \
--to=chenridong@huaweicloud.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llong@redhat.com \
--cc=lujialin4@huawei.com \
--cc=mkoutny@suse.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®