From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: "Zefan Li" <lizefan.x@bytedance.com>,
"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-cgroup 0/2] cgroup/cpuset: Account for boot time isolated CPUs
Date: Fri, 30 Aug 2024 09:24:50 -1000 [thread overview]
Message-ID: <ZtIcgpKqtZ89RlT5@slm.duckdns.org> (raw)
In-Reply-To: <20240820195536.202066-1-longman@redhat.com>
On Tue, Aug 20, 2024 at 03:55:34PM -0400, Waiman Long wrote:
> The current cpuset code and test_cpuset_prs.sh test have not fully
> account for the possibility of pre-isolated CPUs added by the "isolcpus"
> boot command line parameter. This patch series modifies them to do the
> right thing whether or not "isolcpus" is present or not.
>
> The updated test_cpuset_prs.sh was run successfully with or without the
> "isolcpus" option.
>
> Waiman Long (2):
> cgroup/cpuset: Account for boot time isolated CPUs
> selftest/cgroup: Make test_cpuset_prs.sh deal with pre-isolated CPUs
Applied 1-2 to cgroup/for-6.12.
Thanks.
--
tejun
prev parent reply other threads:[~2024-08-30 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 19:55 [PATCH-cgroup 0/2] cgroup/cpuset: Account for boot time isolated CPUs Waiman Long
2024-08-20 19:55 ` [PATCH-cgroup 1/2] " Waiman Long
2024-08-27 8:01 ` Michal Koutný
2024-08-28 0:07 ` Waiman Long
2024-08-20 19:55 ` [PATCH-cgroup 2/2] selftest/cgroup: Make test_cpuset_prs.sh deal with pre-isolated CPUs Waiman Long
2024-08-26 19:01 ` [PATCH-cgroup 0/2] cgroup/cpuset: Account for boot time isolated CPUs Waiman Long
2024-08-26 19:05 ` Tejun Heo
2024-08-26 19:41 ` Waiman Long
2024-08-26 20:16 ` Tejun Heo
2024-08-30 19:24 ` Tejun Heo [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=ZtIcgpKqtZ89RlT5@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=shuah@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