All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ridong Chen <ridong.chen@linux.dev>
To: "Waiman Long" <longman@redhat.com>, "Tejun Heo" <tj@kernel.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Shuah Khan" <shuah@kernel.org>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH-next v3 0/3] cgroup/cpuset: Support multiple destination cpusets for cpuset_*attach()
Date: Tue, 14 Jul 2026 16:57:45 +0800	[thread overview]
Message-ID: <007856c9-3506-4888-9818-8e4630b37fdc@linux.dev> (raw)
In-Reply-To: <20260712235510.373125-1-longman@redhat.com>



On 7/13/2026 7:55 AM, Waiman Long wrote:
>   v3:
>    - Swap the first 2 patches as the original patch 1 can introduce serious bug
>      without patch 2. Doing patch 2 first will be less problematic.
> 

Would it make sense to squash these two patches into one?

>   v2: https://lore.kernel.org/lkml/20260712150127.236790-1-longman@redhat.com
>    - Make sure that attach_ctx.old_cs won't be set to a source cpuset that is
>      also the destination cpuset.
> 
>   v1: https://lore.kernel.org/lkml/20260711020540.176740-1-longman@redhat.com
> 
> This is a follow-up patch series to [1] to properly handle a special case
> for cpuset task migration operation where the source and destination
> cpusets are the same.
> 
> Patch 1 enables cpuset_*attach() to handle the case where there are many
> destination cpusets from enabling cpuset controller. Patch 2 handles
> those tasks that have the same source and destination cpuset by skipping
> them as they are not migrating with respect to cpuset. Patch 3 adds a
> new test case into test_cpuset to test proper handling of cpu affinity
> when cpuset controller is disabled.
> 
> [1] https://lore.kernel.org/lkml/20260702214757.579012-1-longman@redhat.com
> 
> Michal Koutný (1):
>    selftests/cgroup: Add test for cpuset affinity on controller disable
> 
> Waiman Long (2):
>    cgroup/cpuset: Support multiple destination cpusets for
>      cpuset_*attach()
>    cgroup/cpuset: Handle the special case of non-moving tasks in
>      cpuset_can_attach()
> 
>   kernel/cgroup/cpuset.c                       | 131 ++++++----
>   tools/testing/selftests/cgroup/test_cpuset.c | 243 +++++++++++++++++++
>   2 files changed, 321 insertions(+), 53 deletions(-)
> 

-- 
Best regards
Ridong


  parent reply	other threads:[~2026-07-14  8:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-12 23:55 [PATCH-next v3 0/3] cgroup/cpuset: Support multiple destination cpusets for cpuset_*attach() Waiman Long
2026-07-12 23:55 ` [PATCH-next v3 1/3] " Waiman Long
2026-07-12 23:55 ` [PATCH-next v3 2/3] cgroup/cpuset: Handle the special case of non-moving tasks in cpuset_can_attach() Waiman Long
2026-07-12 23:55 ` [PATCH-next v3 3/3] selftests/cgroup: Add test for cpuset affinity on controller disable Waiman Long
2026-07-14  8:57 ` Ridong Chen [this message]
2026-07-16 19:47   ` [PATCH-next v3 0/3] cgroup/cpuset: Support multiple destination cpusets for cpuset_*attach() Waiman Long
2026-07-16 19:42 ` Tejun Heo
2026-07-16 19:47   ` 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=007856c9-3506-4888-9818-8e4630b37fdc@linux.dev \
    --to=ridong.chen@linux.dev \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mkoutny@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.