public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: mtk.manpages@gmail.com, Peter Zijlstra <peterz@infradead.org>,
	cgroups@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
	linux-man <linux-man@vger.kernel.org>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	Mike Galbraith <efault@gmx.de>, Li Zefan <lizefan@huawei.com>,
	Ingo Molnar <mingo@redhat.com>, Paul Turner <pjt@google.com>,
	kernel-team@fb.com, Andy Lutomirski <luto@amacapital.net>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Lauro Venancio <lvenanci@redhat.com>,
	Waiman Long <longman@redhat.com>
Subject: Re: cgroups(7): documenting cgroups v2 thread mode
Date: Tue, 9 Jan 2018 23:54:03 +0100	[thread overview]
Message-ID: <5c9ea5dd-12dc-99d6-7905-40fdbc34e6ae@gmail.com> (raw)
In-Reply-To: <20180109211000.GT3668920@devbig577.frc2.facebook.com>

On 01/09/2018 10:10 PM, Tejun Heo wrote:
> Hello,
> 
> On Tue, Jan 02, 2018 at 07:24:01PM +0100, Michael Kerrisk (man-pages) wrote:
>>        2. We write the string "threaded" to each of the domain invalid
>>           cgroups  under  y,  in  order  to  convert  them to the type
>>           threaded.  As a consequence of this step, all threads  under
>>           the  threaded  root  now  have  the  type  threaded  and the
>>           threaded subtree is now fully usable.   The  requirement  to
>>           write  "threaded"  to each of these cgroups is somewhat cum‐
>>           bersome, but allows for possible future  extensions  to  the
>>           thread-mode model.
>>
>>           ┌─────────────────────────────────────────────────────┐
>>           │FIXME                                                │
>>           ├─────────────────────────────────────────────────────┤
>>           │Re  the preceding paragraphs... Are there other rea‐ │
>>           │sosn  for  the  (cumbersome)  requirement  to  write │
>>           │'threaded'  to  each of the cgroup.type files in the │
>>           │threaded subtrees? Tejun Heo mentioned  the  follow‐ │
>>           │ing:                                                 │
>>           │                                                     │
>>           │    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.                             │
>>           │                                                     │
>>           │But,  it's  not  clear  to  me  how  "Doing that for │
>>           │cgroups further  down  in  the  hierarchy  would  be │
>>           │really inconsistent", since in the current implemen‐ │
>>           │tation, those same thread groups  are  converted  to │
>>           │"domain invalid" type.  What am I missing?           │
>>           └─────────────────────────────────────────────────────┘
> 
> Yeah, I was confused with an earlier varient where we were marking
> threaded domains instead of threaded roots.  It's mostly about future
> extensibility (especially as Waiman was proposing related changes
> there) and not doing things automatically / recursively if possible.
> 
> Looks good to me.

One more thing. I added the following sentence to the text:

       The  cgroup.threads file is writable only for the cgroups inside a
       threaded subtree.

Can you confirm that that is correct, please.

Cheers,

Michael



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

  parent reply	other threads:[~2018-01-09 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 18:24 cgroups(7): documenting cgroups v2 thread mode Michael Kerrisk (man-pages)
2018-01-09 21:10 ` Tejun Heo
     [not found]   ` <20180109211000.GT3668920-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2018-01-09 22:52     ` Michael Kerrisk (man-pages)
2018-01-09 22:54   ` Michael Kerrisk (man-pages) [this message]
     [not found]     ` <5c9ea5dd-12dc-99d6-7905-40fdbc34e6ae-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-10 14:47       ` Tejun Heo
     [not found]         ` <20180110144708.GC3668920-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2018-01-10 22:18           ` Michael Kerrisk (man-pages)
     [not found]             ` <704d0cd5-0bab-f876-a09c-9d60e9d2ef93-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-10 22:29               ` Tejun Heo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5c9ea5dd-12dc-99d6-7905-40fdbc34e6ae@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=efault@gmx.de \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=longman@redhat.com \
    --cc=luto@amacapital.net \
    --cc=lvenanci@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=serge@hallyn.com \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox