[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170831094145.mrz6daucapq5kvn7@gmail.com>
Date: Thu, 31 Aug 2017 11:41:47 +0200
From: Christian Brauner <christian.brauner@...onical.com>
To: Tejun Heo <tj@...nel.org>
Cc: christian.brauner@...ntu.com, Li Zefan <lizefan@...wei.com>,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
w.bumiller@...xmox.com, stgraber@...ntu.com, serge@...lyn.com
Subject: Re: [lxc-devel] [RFC PATCH] cgroup, cpuset: add cpuset.remap_cpus
On Wed, Aug 30, 2017 at 05:41:31PM -0700, Tejun Heo wrote:
> 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.
Cool. If it can be done easier and less invasive I'm all for it. Did the patch
already make it into your branch and - only if you happen to have the reference
flying around - could you point me to it.
Thanks!
Christian
>
> Thanks.
>
> --
> tejun
Powered by blists - more mailing lists