public inbox for cgroups@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Petr Malat <oss@malat.biz>
Cc: cgroups@vger.kernel.org, longman@redhat.com
Subject: Re: [PATCH] cgroup/cpuset: Make cpuset.cpus.effective independent of cpuset.cpus
Date: Mon, 25 Mar 2024 10:12:29 -1000	[thread overview]
Message-ID: <ZgHarUDknkJyidia@slm.duckdns.org> (raw)
In-Reply-To: <20240321213945.1117641-1-oss@malat.biz>

On Thu, Mar 21, 2024 at 10:39:45PM +0100, Petr Malat wrote:
> Requiring cpuset.cpus.effective to be a subset of cpuset.cpus makes it
> hard to use as one is forced to configure cpuset.cpus of current and all
> ancestor cgroups, which requires a knowledge about all other units
> sharing the same cgroup subtree. Also, it doesn't allow using empty
> cpuset.cpus.
> 
> Do not require cpuset.cpus.effective to be a subset of cpuset.cpus and
> create remote cgroup only if cpuset.cpus is empty, to make it easier for
> the user to control which cgroup is being created.
> 
> Signed-off-by: Petr Malat <oss@malat.biz>

Waiman, what do you think?

Thanks.

-- 
tejun

  reply	other threads:[~2024-03-25 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 21:33 [RFC/POC]: Make cpuset.cpus.effective independent of cpuset.cpus Petr Malat
2024-03-21 21:39 ` [PATCH] cgroup/cpuset: " Petr Malat
2024-03-25 20:12   ` Tejun Heo [this message]
2024-03-26 15:14     ` Waiman Long
2024-03-26 16:17       ` Tejun Heo
2024-04-02 17:04   ` Michal Koutný
2024-04-04  4:36     ` Petr Malat
2024-04-04  8:09       ` Michal Koutný
2024-03-22  1:41 ` [RFC/POC]: " Waiman Long
2024-03-22  5:54   ` Petr Malat

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=ZgHarUDknkJyidia@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=oss@malat.biz \
    /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