On Tue, Feb 23, 2016 at 04:58:37PM +0100, Henning Schild wrote:
> When using a hierarchy of cgroups we might want to add tasks just to
> the children cgroups but never to the parent. To make sure we do not
> use a parent cgroup by accident add a mechanism that lets us assert
> a correct implementat
Ok i will reorder, fix style and docs etc.
On Thu, 25 Feb 2016 17:52:55 -0500
John Ferlan wrote:
> On 02/23/2016 10:58 AM, Henning Schild wrote:
> > When using a hierarchy of cgroups we might want to add tasks just to
> > the children cgroups but never to the parent. To make sure we do not
> > u
On 02/23/2016 10:58 AM, Henning Schild wrote:
> When using a hierarchy of cgroups we might want to add tasks just to
> the children cgroups but never to the parent. To make sure we do not
> use a parent cgroup by accident add a mechanism that lets us assert
> a correct implementation in cases we
When using a hierarchy of cgroups we might want to add tasks just to
the children cgroups but never to the parent. To make sure we do not
use a parent cgroup by accident add a mechanism that lets us assert
a correct implementation in cases we want such a hierarchy.
i.e. for qemu cpusets we want al