[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180110221418.GF3460072@devbig577.frc2.facebook.com>
Date: Wed, 10 Jan 2018 14:14:18 -0800
From: Tejun Heo <tj@...nel.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Cc: "Serge E. Hallyn" <serge@...lyn.com>,
linux-man <linux-man@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>, cgroups@...r.kernel.org,
Roman Gushchin <guro@...com>
Subject: Re: cgroups(7): documenting cgroups v2 delegation
Hello, Michael.
On Wed, Jan 10, 2018 at 11:01:11PM +0100, Michael Kerrisk (man-pages) wrote:
> >>>> Can you please confirm that it's only necessary to delegate this file
> >>>> if we are delegating a threaded subtree?
> >>>
> >>> Replied on the other thread. The file isn't delegatable as far as I
> >>> can tell.
> >>
> >> So, following on from the discussion in the other thread, my
> >> question above still stands.
> >
> > Oh, I frankly haven't thought about delegating a threaded subtree.
>
> I'm still confused. cgroup-v2.txt documents the possibility. You
> wrote that text. We just had a conversation in another thread about the
> fact that cgroup.threads is delegatable. You must have thought at
> least a little about this?
Oh, I'm probably mixing up two things.
1. When delegating, cgroup.threads should be delegated. Doing that
selectively doesn't achieve anything meaningful.
2. I haven't thought much about delegating a sub-protion of a threaded
subtree. Everything works the same way. I just can't think of a
use case.
Thanks.
--
tejun
Powered by blists - more mailing lists