mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Zefan Li <lizefan.x@bytedance.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Jonathan Corbet <corbet@lwn.net>, Shuah Khan <shuah@kernel.org>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
	Xavier <ghostxavier@sina.com>, Peter Hunt <pehunt@redhat.com>,
	Petr Malat <oss@malat.biz>
Subject: Re: [PATCH-cgroup v2 0/5] cgroup/cpuset: Fix miscellaneous issues
Date: Wed, 19 Jun 2024 07:38:31 -1000	[thread overview]
Message-ID: <ZnMXl5mS5zUHp7rS@slm.duckdns.org> (raw)
In-Reply-To: <20240617143945.454888-1-longman@redhat.com>

On Mon, Jun 17, 2024 at 10:39:40AM -0400, Waiman Long wrote:
>  v2:
>   - Fix test_cpuset_prs.sh problems reported by test robot
>   - Relax restriction imposed between cpuset.cpus.exclusive and
>     cpuset.cpus of sibling cpusets.
>   - Make cpuset.cpus.exclusive independent of cpuset.cpus. 
>   - Update test_cpuset_prs.sh accordingly.
>   
>  [v1] https://lore.kernel.org/lkml/20240605171858.1323464-1-longman@redhat.com/
> 
> This patchset attempts to address the following cpuset issues.
>  1) While reviewing the generate_sched_domains() function, I found a bug
>     in generating sched domains for remote non-isolating partitions.
>  2) Test robot had reported a test_cpuset_prs.sh test failure.
>  3) The current exclusivity test between cpuset.cpus.exclusive and
>     cpuset.cpus and the restriction that the set effective exclusive
>     CPUs has to be a subset of cpuset.cpus make it harder to preconfigure
>     the cgroup hierarchy to enable remote partition.
> 
> The test_cpuset_prs.sh script is updated to match changes made in this
> patchset and was run to verify that the new code did not cause any
> regression.

Applied to cgroup/for-6.11.

Thanks.

-- 
tejun

      parent reply	other threads:[~2024-06-19 17:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 14:39 Waiman Long
2024-06-17 14:39 ` [PATCH-cgroup v2 1/5] cgroup/cpuset: Fix remote root partition creation problem Waiman Long
2024-06-17 14:39 ` [PATCH-cgroup v2 2/5] selftest/cgroup: Fix test_cpuset_prs.sh problems reported by test robot Waiman Long
2024-06-17 14:39 ` [PATCH-cgroup v2 3/5] cgroup/cpuset: Delay setting of CS_CPU_EXCLUSIVE until valid partition Waiman Long
2024-06-17 14:39 ` [PATCH-cgroup v2 4/5] cgroup/cpuset: Make cpuset.cpus.exclusive independent of cpuset.cpus Waiman Long
2024-07-15 15:56   ` Petr Malat
2024-07-15 19:17     ` Waiman Long
2024-06-17 14:39 ` [PATCH-cgroup v2 5/5] selftest/cgroup: Update test_cpuset_prs.sh to match changes Waiman Long
2024-06-19 17:38 ` 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=ZnMXl5mS5zUHp7rS@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=ghostxavier@sina.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=longman@redhat.com \
    --cc=oss@malat.biz \
    --cc=pehunt@redhat.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

all inboxes | Powered by JetHome®