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>,
	"Shuah Khan" <shuah@kernel.org>,
	"Juri Lelli" <juri.lelli@redhat.com>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Aaron Tomlin <atomlin@atomlin.com>,
	Guopeng Zhang <guopeng.zhang@linux.dev>
Subject: Re: [PATCH-next v10 10/11] cgroup/cpuset: Support multiple destination cpusets for cpuset_*attach()
Date: Fri, 3 Jul 2026 01:56:41 -0400	[thread overview]
Message-ID: <7d40ab06-7f1c-4cd8-84a0-552c53e2ca20@redhat.com> (raw)
In-Reply-To: <5a8b4500-7cab-4ef6-ae96-b0f794ee51a9@linux.dev>

On 7/2/26 11:31 PM, Ridong Chen wrote:
>
>
> On 7/3/2026 5:47 AM, Waiman Long wrote:
>> The only case where the cgroup_taskset structure requires task migration
>> to multiple cpusets is when enabling a cpuset controller in cgroup v2
>> where the newly created child cpusets inherits the same effective CPUs
>> and memory nodes from the parent. In that case, task migration can 
>> happen
>> directly with no update to tasks' CPU and memory nodes assignment and no
>> further work needed from the cpuset side except updating 
>> nr_deadline_tasks
>> when DL tasks are involved and setting old_mems_allowed in the child
>> cpusets.
>>
>> Do that by tracking all the destination cpusets with a new dst_cs_head
>> singly linked list. The reset_migrate_dl_data() function is integrated
>> into clear_attach_data() so that it can be used for both source and
>> destination cpusets.
>>
>> It is assumed that a given cpuset cannot be both a source and a
>> destination cpuset. If such condition happens or when there are multiple
>> destination cpusets with CPU or memory nodes changes, the current code
>> will not handle it correctly. So it will print a warning and fail the
>> attach operation in these unexpected cases as we will have to enhance 
>> the
>> code to support this if such use cases are valid and not coding errors.
>>
>> Signed-off-by: Waiman Long <longman@redhat.com>
>> ---
>>   kernel/cgroup/cpuset-internal.h |   1 +
>>   kernel/cgroup/cpuset.c          | 115 ++++++++++++++++++++------------
>>   2 files changed, 72 insertions(+), 44 deletions(-)
>>
>> diff --git a/kernel/cgroup/cpuset-internal.h 
>> b/kernel/cgroup/cpuset-internal.h
>> index e7d010661fd3..d1161b0a3d85 100644
>> --- a/kernel/cgroup/cpuset-internal.h
>> +++ b/kernel/cgroup/cpuset-internal.h
>> @@ -149,6 +149,7 @@ struct cpuset {
>>        * For linking impacted cpusets during an attach operation.
>>        */
>>       struct llist_node attach_node;
>> +    bool attach_source;
>>         /* partition root state */
>>       int partition_root_state;
>> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
>> index 4bbfae041b63..cf14dc506a40 100644
>> --- a/kernel/cgroup/cpuset.c
>> +++ b/kernel/cgroup/cpuset.c
>> @@ -366,10 +366,12 @@ static struct {
>>       bool cpus_updated;
>>       bool mems_updated;
>>       bool task_work_queued;
>> +    bool many_dest_cs;    /* Have many destination cpusets */
>>       struct cpuset *old_cs;    /* Source cpuset */
>>       nodemask_t nodemask_to;
>>   } attach_ctx;
>>   static LLIST_HEAD(src_cs_head);
>> +static LLIST_HEAD(dst_cs_head);
>
> Nit.
>
> Would it make sense to move src_cs_head/dst_cs_head into attach_ctx?

I had thought about it, but it is more simple to just use LIST_HEAD() 
macro than explicitly initialize just the two llist_head's in the structure.

Cheers,
Longman

>
>>   /*
>>    * Wait if task attach is in progress until it is done and then 
>> acquire
>> @@ -3044,8 +3046,23 @@ static int cpuset_can_attach_check(struct 
>> cpuset *cs, struct cpuset *oldcs,
>>       if (!oldcs)
>>           return 0;
>>   -    if (!llist_on_list(&oldcs->attach_node))
>> +    /*
>> +     * The same cpuset cannot be both a source and a destination.
>> +     * The current code does not support that, print a warning and
>> +     * fail the attach if so.
>> +     */
>> +    if (WARN_ON_ONCE((!oldcs->attach_source &&
>> +              llist_on_list(&oldcs->attach_node)) ||
>> +              cs->attach_source))
>> +        return -EINVAL;
>> +
>> +    if (!llist_on_list(&oldcs->attach_node)) {
>>           llist_add(&oldcs->attach_node, &src_cs_head);
>> +        oldcs->attach_source = true;
>> +    }
>> +
>> +    if (!llist_on_list(&cs->attach_node))
>> +        llist_add(&cs->attach_node, &dst_cs_head);
>>         cpus_updated = !cpumask_equal(cs->effective_cpus, 
>> oldcs->effective_cpus);
>>       mems_updated = !nodes_equal(cs->effective_mems, 
>> oldcs->effective_mems);
>> @@ -3075,35 +3092,31 @@ static int cpuset_can_attach_check(struct 
>> cpuset *cs, struct cpuset *oldcs,
>>       return 0;
>>   }
>>   -static int cpuset_reserve_dl_bw(struct cpuset *cs)
>> +static int cpuset_reserve_dl_bw(void)
>>   {
>> +    struct cpuset *cs;
>>       int cpu, ret;
>>   -    if (!cs->sum_migrate_dl_bw)
>> -        return 0;
>> +    llist_for_each_entry(cs, dst_cs_head.first, attach_node) {
>> +        if (!cs->sum_migrate_dl_bw)
>> +            continue;
>>   -    cpu = cpumask_any_and(cpu_active_mask, cs->effective_cpus);
>> -    if (unlikely(cpu >= nr_cpu_ids))
>> -        return -EINVAL;
>> +        cpu = cpumask_any_and(cpu_active_mask, cs->effective_cpus);
>> +        if (unlikely(cpu >= nr_cpu_ids))
>> +            return -EINVAL;
>>   -    ret = dl_bw_alloc(cpu, cs->sum_migrate_dl_bw);
>> -    if (ret)
>> -        return ret;
>> +        ret = dl_bw_alloc(cpu, cs->sum_migrate_dl_bw);
>> +        if (ret)
>> +            return ret;
>>   -    cs->dl_bw_cpu = cpu;
>> +        cs->dl_bw_cpu = cpu;
>> +    }
>>       return 0;
>>   }
>>   -static void reset_migrate_dl_data(struct cpuset *cs)
>> -{
>> -    cs->nr_migrate_dl_tasks = 0;
>> -    cs->sum_migrate_dl_bw = 0;
>> -    cs->dl_bw_cpu = -1;
>> -}
>> -
>>   /*
>>    * Clear and optionally apply (@cancel is false) the attach related 
>> data in the
>> - * source cpusets.
>> + * source or destination cpuset.
>>    */
>>   static void clear_attach_data(struct llist_head *head, bool cancel)
>>   {
>> @@ -3115,8 +3128,13 @@ static void clear_attach_data(struct 
>> llist_head *head, bool cancel)
>>           if (cs->nr_migrate_dl_tasks) {
>>               if (!cancel)
>>                   atomic_add(cs->nr_migrate_dl_tasks, 
>> &cs->nr_deadline_tasks);
>> +            else if (cs->dl_bw_cpu >= 0) /* && cacnel */
>> +                dl_bw_free(cs->dl_bw_cpu, cs->sum_migrate_dl_bw);
>>               cs->nr_migrate_dl_tasks = 0;
>> +            cs->sum_migrate_dl_bw = 0;
>> +            cs->dl_bw_cpu = -1;
>>           }
>> +        cs->attach_source = false;
>>       }
>>   }
>>   @@ -3137,6 +3155,7 @@ static int cpuset_can_attach(struct 
>> cgroup_taskset *tset)
>>       mutex_lock(&cpuset_mutex);
>>       attach_ctx.cpus_updated = false;
>>       attach_ctx.mems_updated = false;
>> +    attach_ctx.many_dest_cs = false;
>>         /* Check to see if task is allowed in the cpuset */
>>       ret = cpuset_can_attach_check(cs, oldcs, &setsched_check);
>> @@ -3161,9 +3180,13 @@ static int cpuset_can_attach(struct 
>> cgroup_taskset *tset)
>>        * selected as attach_ctx.old_cs.
>>        */
>>       cgroup_taskset_for_each(task, css, tset) {
>> +        struct cpuset *new_cs = css_cs(css);
>>           struct cpuset *new_oldcs = task_cs(task);
>>   -        if (new_oldcs != oldcs) {
>> +        if ((new_oldcs != oldcs) || (new_cs != cs)) {
>> +            if (new_cs != cs)
>> +                attach_ctx.many_dest_cs = true;
>> +            cs = new_cs;
>>               oldcs = new_oldcs;
>>               ret = cpuset_can_attach_check(cs, oldcs, &setsched_check);
>>               if (ret)
>> @@ -3197,12 +3220,28 @@ static int cpuset_can_attach(struct 
>> cgroup_taskset *tset)
>>           }
>>       }
>>   -    ret = cpuset_reserve_dl_bw(cs);
>> +    /*
>> +     * The only case where there are multiple destination cpusets for
>> +     * task migration is when enabling a v2 cpuset controllers where
>> +     * tasks will be migrated to multiple child cpusets from a parent
>> +     * cpuset with the same effective CPUs and memory nodes. IOW,
>> +     * both attach_cpus_updated and attach_mems_updated should be 
>> false.
>> +     * If not, it is a condition that the current code cannot handled.
>> +     * Print a warning and abort the attach operation as further code
>> +     * change will be needed.
>> +     */
>> +    if (WARN_ON_ONCE(attach_ctx.many_dest_cs && (!cpuset_v2() ||
>> +             attach_ctx.cpus_updated || attach_ctx.mems_updated))) {
>> +        ret = -EINVAL;
>> +        goto out_unlock;
>> +    }
>> +
>> +    ret = cpuset_reserve_dl_bw();
>>     out_unlock:
>>       if (ret) {
>> -        reset_migrate_dl_data(cs); /* Destination cpuset only */
>>           clear_attach_data(&src_cs_head, true);
>> +        clear_attach_data(&dst_cs_head, true);
>>       } else {
>>           attach_ctx.in_progress++;
>>       }
>> @@ -3213,22 +3252,10 @@ static int cpuset_can_attach(struct 
>> cgroup_taskset *tset)
>>     static void cpuset_cancel_attach(struct cgroup_taskset *tset)
>>   {
>> -    struct cgroup_subsys_state *css;
>> -    struct cpuset *cs;
>> -
>> -    cgroup_taskset_first(tset, &css);
>> -    cs = css_cs(css);
>> -
>>       mutex_lock(&cpuset_mutex);
>>       dec_attach_in_progress_locked();
>>       clear_attach_data(&src_cs_head, true);
>> -
>> -    if (cs->dl_bw_cpu >= 0)
>> -        dl_bw_free(cs->dl_bw_cpu, cs->sum_migrate_dl_bw);
>> -
>> -    if (cs->nr_migrate_dl_tasks)
>> -        reset_migrate_dl_data(cs);
>> -
>> +    clear_attach_data(&dst_cs_head, true);
>>       mutex_unlock(&cpuset_mutex);
>>   }
>>   @@ -3311,25 +3338,25 @@ static void cpuset_attach(struct 
>> cgroup_taskset *tset)
>>        * In the default hierarchy, enabling cpuset in the child cgroups
>>        * will trigger a cpuset_attach() call with no change in 
>> effective cpus
>>        * and mems. In that case, we can optimize out by skipping the 
>> task
>> -     * iteration and update.
>> +     * iteration and updatebut the destination cpuset list is 
>> iterated to
>      updatebut -> update, but?> +     * set old_mems_allowed.
>>        */
>> -    if (cpuset_v2() && !attach_ctx.cpus_updated && 
>> !attach_ctx.mems_updated)
>> +    if (cpuset_v2() && !attach_ctx.cpus_updated && 
>> !attach_ctx.mems_updated) {
>> +        llist_for_each_entry(cs, dst_cs_head.first, attach_node)
>> +            cs->old_mems_allowed = attach_ctx.nodemask_to;
>>           goto out;
>> +    }
>>   +    /* Task iteration shouldn't happen with 
>> attach_ctx.many_dest_cs set */
>>       cgroup_taskset_for_each(task, css, tset)
>>           cpuset_attach_task(cs, task);
>>   -out:
>>       if (attach_ctx.task_work_queued)
>>           schedule_flush_migrate_mm();
>>       cs->old_mems_allowed = attach_ctx.nodemask_to;
>> -
>> -    if (cs->nr_migrate_dl_tasks) {
>> -        atomic_add(cs->nr_migrate_dl_tasks, &cs->nr_deadline_tasks);
>> -        reset_migrate_dl_data(cs);
>> -    }
>> -
>> +out:
>>       clear_attach_data(&src_cs_head, false);
>> +    clear_attach_data(&dst_cs_head, false);
>>       dec_attach_in_progress_locked();
>>         mutex_unlock(&cpuset_mutex);
>
> Reviewed-by: Ridong Chen <ridong.chen@linux.dev>
>


  reply	other threads:[~2026-07-03  5:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 21:47 [PATCH-next v10 00/11] cgroup/cpuset: Support multiple source/destination cpusets for cpuset_*attach() Waiman Long
2026-07-02 21:47 ` [PATCH-next v10 01/11] cgroup/cpuset: Make nr_deadline_tasks an atomic_t Waiman Long
2026-07-02 21:47 ` [PATCH-next v10 02/11] cgroup/cpuset: Fix node inconsistencies between cpuset_update_tasks_nodemask() and cpuset_attach() Waiman Long
2026-07-02 21:47 ` [PATCH-next v10 03/11] cgroup/cpuset: Prevent race between task attach and cpuset state change Waiman Long
2026-07-02 21:47 ` [PATCH-next v10 04/11] cgroup/cpuset: Put all task attach related variables into attach_ctx Waiman Long
2026-07-02 21:47 ` [PATCH-next v10 05/11] cgroup/cpuset: Add a cpuset_reserve_dl_bw() helper Waiman Long
2026-07-02 21:47 ` [PATCH-next v10 06/11] cgroup/cpuset: Expand the scope of cpuset_can_attach_check() Waiman Long
2026-07-02 21:47 ` [PATCH-next v10 07/11] cgroup/cpuset: Make attach_ctx.old_cs track task group leader Waiman Long
2026-07-02 21:47 ` [PATCH-next v10 08/11] cgroup/cpuset: Move mpol_rebind_mm/cpuset_migrate_mm() calls inside cpuset_attach_task() Waiman Long
2026-07-02 21:47 ` [PATCH-next v10 09/11] cgroup/cpuset: Support multiple source cpusets for cpuset_*attach() Waiman Long
2026-07-03  2:20   ` Ridong Chen
2026-07-02 21:47 ` [PATCH-next v10 10/11] cgroup/cpuset: Support multiple destination " Waiman Long
2026-07-03  3:31   ` Ridong Chen
2026-07-03  5:56     ` Waiman Long [this message]
2026-07-07  0:57   ` Tejun Heo
2026-07-02 21:47 ` [PATCH-next v10 11/11] selftests/cgroup: Add test for cpuset affinity on controller disable Waiman Long
2026-07-07  7:15 ` [PATCH-next v10 00/11] cgroup/cpuset: Support multiple source/destination cpusets for cpuset_*attach() 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=7d40ab06-7f1c-4cd8-84a0-552c53e2ca20@redhat.com \
    --to=longman@redhat.com \
    --cc=atomlin@atomlin.com \
    --cc=cgroups@vger.kernel.org \
    --cc=guopeng.zhang@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=ridong.chen@linux.dev \
    --cc=shuah@kernel.org \
    --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