From: Tejun Heo <tj@kernel.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Writing "+pids" to cgroup.subtree_control flie yields EINVAL
Date: Mon, 4 Dec 2017 13:47:10 -0800 [thread overview]
Message-ID: <20171204214710.GM2421075@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <b2794e0c-1b00-fb81-4d6a-00a2382c7676@gmail.com>
Hello, Michael.
On Mon, Dec 04, 2017 at 10:35:13PM +0100, Michael Kerrisk (man-pages) wrote:
> I was trying to do some simple testing ot the CPU controller
> that is merged into 4.15, and ran immediately into some confusion.
> In the root cgroup on a freshly booted 4.150-rc1, I try the following:
>
> # pwd
> /sys/fs/cgroup/unified
> # echo '+cpu' > cgroup.subtree_control
> sh: echo: write error: Invalid argument
>
> What am I missing> I presume I'm missing something obvious, although
> nothing jumped out at me as I read the cgroups-v2.txt file.
Checking whether I messed up something really basic... hmmm doesn't
seem that way. What do /sys/fs/cgroup/unified/cgroup.controllers and
/proc/cgroups say?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-12-04 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 21:35 Writing "+pids" to cgroup.subtree_control flie yields EINVAL Michael Kerrisk (man-pages)
2017-12-04 21:47 ` Tejun Heo [this message]
2017-12-05 7:45 ` Michael Kerrisk (man-pages)
2017-12-05 16:00 ` Tejun Heo
2017-12-05 16:44 ` Michael Kerrisk (man-pages)
2017-12-05 17:13 ` [PATCH cgroup/for-4.15-fixes] cgroup: add warning about RT not being supported on cgroup2 Tejun Heo
2017-12-05 18:24 ` Michael Kerrisk (man-pages)
2017-12-05 18:29 ` [PATCH v2 " Tejun Heo
2017-12-05 18:53 ` Michael Kerrisk (man-pages)
2017-12-05 19:48 ` 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=20171204214710.GM2421075@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.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 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.