Message-ID: <CAKgNAkhWhw8LNBdVZPzZ73VOmXDrxzSUD862AHduAhs3CF0bNw@mail.gmail.com>
Date:   Fri, 22 Dec 2017 10:11:00 +0100
From:   "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
To:     Tejun Heo <tj@...nel.org>
Cc:     Peter Zijlstra <peterz@...radead.org>, longman@...hat.com,
        lkml <linux-kernel@...r.kernel.org>,
        linux-man <linux-man@...r.kernel.org>,
        "open list:CONTROL GROUP (CGROUP)" <cgroups@...r.kernel.org>
Subject: Re: Cgroups v2 thread mode "domain invalid" state

Hi Tejun,

On 22 December 2017 at 01:15, Tejun Heo <tj@...nel.org> wrote:
> Hello,
>
> On Wed, Dec 20, 2017 at 09:32:04PM +0100, Michael Kerrisk (man-pages) wrote:
>> I did find the July 2017 mail thread
>> "[PATCH 5/6] cgroup: implement cgroup v2 thread support"
>> (https://marc.info/?t=150025735500001&r=1&w=2)
>> where this cgroup type was discussed, but I must admit that I still
>> don't get it. Instead of converting cgroups under a threaded subtree
>> to "domain invalid" type, why can't they just be turned straight into
>> "threaded" type?
>>
>> I guess another way of asking this question is: what possibilities
>> does manually switching each "domain invalid" cgroup to "threaded"
>> allow that wouldn't be allowed by immediately making all of the
>> cgroups in a threaded subtree "threaded"?
>
> IIRC, there were two reasons.  (Writing from memory, so I might not be
> completely accurate.)
>
> * Consistency w/ the cgroups right under the root cgroup.  Because
>   they can be both domains and threadroots, we can't switch the
>   children over to thread mode automatically.  Doing that for cgroups
>   further down in the hierarchy would be really inconsistent.

I don't get the above. I mean, if we have the following hierarchy,
where R is the cgoup v2 mount point:

R---A(d)------B(d)
 \       \----C(d)
  \
   \
    X(d)------Y(d)

And we write "threaded" to A/cgroup.type, then we end up with:

R---A(t)------B(di)
 \       \----C(di)
  \
   \
    X(d)------Y(d)

(To be clear: "(d)" means "domain", "(di)" means "domain invalid", and
"(t)" means "threaded".)

But equally (in another world), that operation could have resulted in:

R---A(t)------B(t)
 \       \----C(t)
  \
   \
    X(d)------Y(d)

It's not clear to me how "Doing that for cgroups further down in the
hierarchy would be really inconsistent", since in the current
implementation, those same thread groups are converted to "domain
invalid" type.  What am I missing?

But, regarding the next point:

> * Possible extension to threadmode.  If we figure out how to do mixed
>   mode further down in the hierarchy (and if there are actual use
>   cases which require that), automatically switching would be really
>   confusing.
>
> The invalid state while not the most convenient is straight forward
> (only the operations which are explicitly asked are performed) and
> keeps the door open for future changes.

The "allowing for future" extensions idea makes some sense to me.

One other point that occurred to me after I wrote my email yesterday
was that if the threaded root reverts from being "domain threaded" to
"domain" (because it no longer has "threaded" children AND either it
has no member processes or it has no threaded controllers enabled),
then the "domain invalid" descendants revert to type "domain". I'm not
sure whether that detail also provides some rationale as to why all
descendants of the threaded root cgroup aren't automatically converted
to type "threaded". Any thoughts about that?

Thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

Powered by blists - more mailing lists