From: Waiman Long <longman@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Ridong Chen" <ridong.chen@linux.dev>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Shuah Khan" <shuah@kernel.org>,
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: Thu, 16 Jul 2026 15:47:57 -0400 [thread overview]
Message-ID: <67d11071-a1f3-4ed5-80fe-3b1d9a330c75@redhat.com> (raw)
In-Reply-To: <597fd8e0d3c2de61aeecd3645a7b8198@kernel.org>
On 7/16/26 3:42 PM, Tejun Heo wrote:
> Hello,
>
> On Sun, Jul 12, 2026 at 07:55:07PM -0400, Waiman Long wrote:
>> 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()
> Applied 1-3 to cgroup/for-7.3.
>
> While applying, fixed a comment typo in patch 1:
>
> - else if (cs->dl_bw_cpu >= 0) /* && cacnel */
> + else if (cs->dl_bw_cpu >= 0) /* && cancel */
>
> The following selftest issues remain. Let's address them with follow-up
> patches:
>
> - cpu_set_equal() iterates sizeof(mask) bytes rather than bits, so only
> CPUs 0-7 are compared, and the assert compares a byte count against
> CPU_SETSIZE bits so it always holds.
>
> - thread_b doesn't wait for thread_a before advancing test_phase to
> AFFINITY_THREADS_READY, so the main thread can read affinity_a_before
> before thread_a has written it.
>
> - On a machine which doesn't have both CPUs 0 and 1 online, the test
> fails instead of skipping.
Will fix the selftest in a follow-up patch.
Cheers,
Longman
prev parent reply other threads:[~2026-07-16 19:48 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 ` [PATCH-next v3 0/3] cgroup/cpuset: Support multiple destination cpusets for cpuset_*attach() Ridong Chen
2026-07-16 19:47 ` Waiman Long
2026-07-16 19:42 ` Tejun Heo
2026-07-16 19:47 ` Waiman Long [this message]
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=67d11071-a1f3-4ed5-80fe-3b1d9a330c75@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--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