Linux cgroups development
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: "Ridong Chen" <ridong.chen@linux.dev>,
	"Tejun Heo" <tj@kernel.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Li Zefan" <lizefan@huawei.com>,
	"Farhad Alemi" <farhad.alemi@berkeley.edu>,
	"Andrew Morton" <akpm@linux-foundation.org>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	Aaron Tomlin <atomlin@atomlin.com>,
	Guopeng Zhang <guopeng.zhang@linux.dev>,
	Gregory Price <gourry@gourry.net>,
	David Hildenbrand <david@kernel.org>
Subject: Re: [PATCH v7 7/9] cgroup/cpuset: Move mpol_rebind_mm/cpuset_migrate_mm() calls inside cpuset_attach_task()
Date: Thu, 25 Jun 2026 14:18:42 -0400	[thread overview]
Message-ID: <7d0ba942-7fd7-404d-a194-82dd05051520@redhat.com> (raw)
In-Reply-To: <e8fb50d3-0831-4caf-b4e4-2af94ac86263@linux.dev>

On 6/21/26 10:48 PM, Ridong Chen wrote:
>
>
> On 6/21/2026 11:28 AM, Waiman Long wrote:
>> The cpuset_attach_task() was introduced in commit 42a11bf5c543
>> ("cgroup/cpuset: Make cpuset_fork() handle CLONE_INTO_CGROUP properly")
>> to enable the CLONE_INTO_CGROUP flag of clone(2) to behave more like
>> moving a task from one cpuset into another one. That commits didn't
>> move the mpol_rebind_mm() and cpuset_migrate_mm() calls for group leader
>> into cpuset_attach_task().
>>
>> When the CLONE_INTO_CGROUP flag is used without CLONE_THREAD, the new
>> task is its own group leader. So it is still not equivalent to moving
>> task between cpusets in this case. Make CLONE_INTO_CGROUP behaves
>> more close to cpuset_attach() by moving the mpol_rebind_mm() and
>> cpuset_migrate_mm() calls inside cpuset_attach_task(). As a result,
>> the following static variables will have to be updated in cpuset_fork().
>>   - cpuset_attach_old_cs
>>   - attach_cpus_updated
>>   - attach_mems_updated
>>   - queue_task_work
>>
>> Signed-off-by: Waiman Long <longman@redhat.com>
>> ---
>>   kernel/cgroup/cpuset.c | 105 ++++++++++++++++++++++++-----------------
>>   1 file changed, 62 insertions(+), 43 deletions(-)
>>
>> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
>> index 0375dae26d0b..511afb077e2d 100644
>> --- a/kernel/cgroup/cpuset.c
>> +++ b/kernel/cgroup/cpuset.c
>> @@ -2981,8 +2981,13 @@ static int update_prstate(struct cpuset *cs, 
>> int new_prs)
>>   /*
>>    * cpuset_can_attach() and cpuset_attach() specific internal data
>>    * Protected by cpuset_mutex
>> + *
>> + * The attach_cpus_updated/attach_mems_updated flags are set in either
>> + * cpuset_attach() or cpuset_fork() and used in cpuset_attach_task().
>>    */
>>   static struct cpuset *cpuset_attach_old_cs;
>> +static bool attach_cpus_updated;
>> +static bool attach_mems_updated;
>>     /*
>>    * Check to see if a cpuset can accept a new task
>> @@ -3157,9 +3162,12 @@ static void cpuset_cancel_attach(struct 
>> cgroup_taskset *tset)
>>    */
>>   static cpumask_var_t cpus_attach;
>>   static nodemask_t cpuset_attach_nodemask_to;
>> +static bool queue_task_work;
>
> There are more and more of these standalone state variables now, and 
> it's getting harder to maintain. Could we group them into a struct and 
> manage them together rather than keep adding globals?
>
> Just like:
>
> ```
> struct cpuset_attach_ctx {
>     struct cpuset     *old_cs;
>     struct llist_head src_cs, dst_cs;
>     bool              cpus_updated, mems_updated, queue_work;
>     nodemask_t        nodemask_to;
> };
> ```

Yes, that makes sense. Will incorporate that in the next version.

Cheers,
Longman


  reply	other threads:[~2026-06-25 18:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-21  3:28 [PATCH v7 0/9] cgroup/cpuset: Support multiple source/destination cpusets for cpuset_*attach() Waiman Long
2026-06-21  3:28 ` [PATCH v7 1/9] cgroup/cpuset: rebind mm mempolicy to effective_mems, not mems_allowed Waiman Long
2026-06-22  1:42   ` Ridong Chen
2026-06-23 16:13   ` Gregory Price
2026-06-21  3:28 ` [PATCH v7 2/9] cgroup/cpuset: Fix node inconsistencies between cpuset_update_tasks_nodemask() and cpuset_attach() Waiman Long
2026-06-23 16:16   ` Gregory Price
2026-06-21  3:28 ` [PATCH v7 3/9] cgroup/cpuset: Prevent race between task attach and cpuset state change Waiman Long
2026-06-22  2:21   ` Ridong Chen
2026-06-25 18:16     ` Waiman Long
2026-06-21  3:28 ` [PATCH v7 4/9] cgroup/cpuset: Add a cpuset_reserve_dl_bw() helper Waiman Long
2026-06-23 16:18   ` Gregory Price
2026-06-21  3:28 ` [PATCH v7 5/9] cgroup/cpuset: Expand the scope of cpuset_can_attach_check() Waiman Long
2026-06-21  3:28 ` [PATCH v7 6/9] cgroup/cpuset: Make cpuset_attach_old_cs track task group leaders Waiman Long
2026-06-21  3:28 ` [PATCH v7 7/9] cgroup/cpuset: Move mpol_rebind_mm/cpuset_migrate_mm() calls inside cpuset_attach_task() Waiman Long
2026-06-22  2:48   ` Ridong Chen
2026-06-25 18:18     ` Waiman Long [this message]
2026-06-21  3:28 ` [PATCH v7 8/9] cgroup/cpuset: Support multiple source cpusets for cpuset_*attach() Waiman Long
2026-06-21  3:28 ` [PATCH v7 9/9] cgroup/cpuset: Support multiple destination " 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=7d0ba942-7fd7-404d-a194-82dd05051520@redhat.com \
    --to=longman@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=atomlin@atomlin.com \
    --cc=cgroups@vger.kernel.org \
    --cc=david@kernel.org \
    --cc=farhad.alemi@berkeley.edu \
    --cc=gourry@gourry.net \
    --cc=guopeng.zhang@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=mkoutny@suse.com \
    --cc=ridong.chen@linux.dev \
    --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