Date: Wed, 30 Aug 2017 17:41:31 -0700
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
Message-ID: <20170831004131.GZ491396@devbig577.frc2.facebook.com>
References: <1482419271-15410-1-git-send-email-w.bumiller@proxmox.com>
 <20170830132755.tnqmuttodexc3oh6@mailbox.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170830132755.tnqmuttodexc3oh6@mailbox.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 812
Lines: 19

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