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 06:26:40 -0800 [thread overview]
Message-ID: <20180110142640.GB3668920@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <672cd179-31be-e03a-f9ff-ce59b76e23e2@gmail.com>
Hello, Michael.
On Tue, Jan 09, 2018 at 11:48:11PM +0100, Michael Kerrisk (man-pages) wrote:
> > That said, not necessarily an objection. I'm just not sure about it.
>
> Okay. For the moment, I'll leave that text as is.
>
> I realized that there was also one more file that needs to be included
> in the list of files that must be delegated:
>
> /dlgt_grp/cgroup.threads
> Changing the ownership of this file is necessary if a
> threaded subtree is being delegated (see the description of
> "thread mode", below).
>
> 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.
Thanks.
--
tejun
next prev parent reply other threads:[~2018-01-10 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 18:22 cgroups(7): documenting cgroups v2 delegation 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 [this message]
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)
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=20180110142640.GB3668920@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=serge@hallyn.com \
/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