All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Roman Gushchin <guro-b10kYP2dOMg@public.gmane.org>
Subject: Re: cgroups(7): documenting cgroups v2 delegation
Date: Wed, 10 Jan 2018 14:14:18 -0800	[thread overview]
Message-ID: <20180110221418.GF3460072@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <fdfc4c27-f87c-fab8-894c-f9f21374bab2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

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
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: "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 14:14:18 -0800	[thread overview]
Message-ID: <20180110221418.GF3460072@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <fdfc4c27-f87c-fab8-894c-f9f21374bab2@gmail.com>

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

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

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 18:22 cgroups(7): documenting cgroups v2 delegation Michael Kerrisk (man-pages)
     [not found] ` <1ce0a885-94fb-7480-7180-7b873c95b1bb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-08 14:14   ` Tejun Heo
2018-01-08 14:14     ` Tejun Heo
     [not found]     ` <20180108141450.GP3668920-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2018-01-08 23:27       ` Michael Kerrisk (man-pages)
2018-01-08 23:27         ` Michael Kerrisk (man-pages)
     [not found]         ` <6c9fdaee-739f-164d-d04e-fb3a7319db90-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-09 21:07           ` Tejun Heo
2018-01-09 21:07             ` Tejun Heo
     [not found]             ` <20180109210722.GS3668920-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2018-01-09 22:48               ` Michael Kerrisk (man-pages)
2018-01-09 22:48                 ` Michael Kerrisk (man-pages)
     [not found]                 ` <672cd179-31be-e03a-f9ff-ce59b76e23e2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-10 14:26                   ` Tejun Heo
2018-01-10 14:26                     ` Tejun Heo
     [not found]                     ` <20180110142640.GB3668920-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2018-01-10 19:20                       ` Michael Kerrisk (man-pages)
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)
     [not found]                             ` <fdfc4c27-f87c-fab8-894c-f9f21374bab2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-10 22:14                               ` Tejun Heo [this message]
2018-01-10 22:14                                 ` Tejun Heo
     [not found]                                 ` <20180110221418.GF3460072-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2018-01-10 22:24                                   ` Michael Kerrisk (man-pages)
2018-01-10 22:24                                     ` Michael Kerrisk (man-pages)
     [not found]                                     ` <5207cfc8-5525-b932-baee-6b0160886178-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-10 22:27                                       ` Tejun Heo
2018-01-10 22:27                                         ` Tejun Heo
     [not found]                                         ` <20180110222726.GG3460072-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2018-01-10 22:34                                           ` Michael Kerrisk (man-pages)
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=20180110221418.GF3460072@devbig577.frc2.facebook.com \
    --to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=guro-b10kYP2dOMg@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.