From: Tejun Heo <tj@kernel.org>
To: christian.brauner@ubuntu.com
Cc: Li Zefan <lizefan@huawei.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
w.bumiller@proxmox.com, stgraber@ubuntu.com, serge@hallyn.com
Subject: Re: [lxc-devel] [RFC PATCH] cgroup, cpuset: add cpuset.remap_cpus
Date: Wed, 30 Aug 2017 17:41:31 -0700 [thread overview]
Message-ID: <20170831004131.GZ491396@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20170830132755.tnqmuttodexc3oh6@mailbox.org>
Hello,
On Wed, Aug 30, 2017 at 03:27:55PM +0200, Christian Brauner wrote:
> The following patch was sent a while back by Wolfgang Bumiller to remap cpusets
> for a whole subtree in a cgroup v1 cpuset hierarchy. The fact that currently
> this is not possible in a non-racy why is a pretty big limitation. This is
> especially true for nested containers. Where the nested containers often create
> additional subcgroups in the cpuset controller at will. The fact that you can't
> *easily* and in a non-racy way tighten the restriction on them after having
> created the parent container's cpuset cgroup seems really troubling.
There was a recent patch to enable v2 behavior on v1, which feels like
the better approach at this point. I'm not sure about adding a whole
new interface for this.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-08-31 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 15:07 [RFC PATCH] cgroup, cpuset: add cpuset.remap_cpus Wolfgang Bumiller
2017-08-30 13:27 ` [lxc-devel] " Christian Brauner
2017-08-31 0:41 ` Tejun Heo [this message]
2017-08-31 9:41 ` Christian Brauner
2017-08-31 13:50 ` Tejun Heo
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=20170831004131.GZ491396@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=serge@hallyn.com \
--cc=stgraber@ubuntu.com \
--cc=w.bumiller@proxmox.com \
/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