mirror of https://lore.kernel.org/lkml/
 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, "Serge E. Hallyn" <serge@hallyn.com>,
	linux-man <linux-man@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	cgroups@vger.kernel.org, Roman Gushchin <guro@fb.com>
Subject: Re: cgroups(7): documenting cgroups v2 delegation
Date: Wed, 10 Jan 2018 23:24:05 +0100	[thread overview]
Message-ID: <5207cfc8-5525-b932-baee-6b0160886178@gmail.com> (raw)
In-Reply-To: <20180110221418.GF3460072@devbig577.frc2.facebook.com>

Hello Tejun,

On 01/10/2018 11:14 PM, Tejun Heo wrote:
> 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.

Understood. But surely delegating cgroup.threads is effectively
meaningless when delegating a "domain" cgroup tree? (Obviously it's
not harmful to delegate the the cgroup.threads file in this case;
it's just not useful to do so.)

> 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.

Ahhh -- now I see what you meant before.

Cheers,

Michael

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

  reply	other threads:[~2018-01-10 22:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 18:22 Michael Kerrisk (man-pages)
2018-01-08 14:14 ` Tejun Heo
2018-01-08 23:27   ` Michael Kerrisk (man-pages)
2018-01-09 21:07     ` Tejun Heo
2018-01-09 22:48       ` Michael Kerrisk (man-pages)
2018-01-10 14:26         ` Tejun Heo
2018-01-10 19:20           ` Michael Kerrisk (man-pages)
2018-01-10 19:39             ` Tejun Heo
2018-01-10 22:01               ` Michael Kerrisk (man-pages)
2018-01-10 22:14                 ` Tejun Heo
2018-01-10 22:24                   ` Michael Kerrisk (man-pages) [this message]
2018-01-10 22:27                     ` Tejun Heo
2018-01-10 22:34                       ` Michael Kerrisk (man-pages)

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=5207cfc8-5525-b932-baee-6b0160886178@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=guro@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®