From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Kernel Newbies <kernelnewbies@kernelnewbies.org>
Subject: Re: newbie-level question about cgroups
Date: Mon, 29 Jul 2019 11:00:20 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1907291054550.13040@localhost.localdomain> (raw)
In-Reply-To: <10729.1564367865@turing-police>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
On Sun, 28 Jul 2019, Valdis Klētnieks wrote:
> On Sun, 28 Jul 2019 15:39:26 -0400, "Robert P. J. Day" said:
>
> > no point bugging the actual cgroup people about this since it
> > should be simple ... if i need *only* cgroup v2, can i dispense
> > entirely with everything under /sys/fs/cgroup/ other than
> > /sys/fs/cgroup/unified?
>
> There's a whole mess of CONFIG_CGROUP_* variables, feel free to turn
> off those that your system doesn't actually need.
>
> Make sure that you keep a backup kernel in case you turn off
> something you shouldn't have. In particular, systemd seems to want
> all sorts of cgroups for no reason other than "because they're
> there".
actually, i just ran across the "cgroup_no_v1=" boot-time parameter:
[KNL] Disable cgroup controllers and named hierarchies in v1
Format: { { controller | "all" | "named" }
[,{ controller | "all" | "named" }...] }
Like cgroup_disable, but only applies to cgroup v1;
the blacklisted controllers remain available in cgroup2.
"all" blacklists all controllers and "named" disables
named mounts. Specifying both "all" and "named" disables
all v1 hierarchies.
so i guess it's not only possible, it's easy. :-)
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2019-07-29 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 19:39 newbie-level question about cgroups Robert P. J. Day
2019-07-29 2:37 ` Valdis Klētnieks
2019-07-29 15:00 ` Robert P. J. Day [this message]
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=alpine.LFD.2.21.1907291054550.13040@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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;
as well as URLs for NNTP newsgroup(s).