From: Cyril Hrubis <chrubis@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: rpalethorpe@suse.com, ltp@lists.linux.it
Subject: Re: [LTP] Question on .needs_cgroup_ctrls for cgroupv2
Date: Mon, 27 Feb 2023 16:28:05 +0100 [thread overview]
Message-ID: <Y/zMBSx4p3gqRC3J@yuki> (raw)
In-Reply-To: <20230227151709.GA12774@localhost>
Hi!
> So .needs_cgroup_ctrls can not used anymore for ONLY V2 case?
> Since i encounter "tst_cgroup.c:848: TCONF: V2 'memory' controller required, but it's mounted on V1" when i add ".needs_cgroup_ctrls = (const char *const []){ "memory", NULL }".
Each controller can be mounted as V1 or as V2 but not both at the same
time. It depends on how the system is booted, the default on most
distributions is mixed V1 and V2 at the moment. If you want V2 system
you have to reboot with systemd.unified_cgroup_hierarchy=1.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-02-27 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 14:44 [LTP] Question on .needs_cgroup_ctrls for cgroupv2 Wei Gao via ltp
2023-02-27 14:58 ` Cyril Hrubis
2023-02-27 15:17 ` Wei Gao via ltp
2023-02-27 15:28 ` Cyril Hrubis [this message]
2023-02-27 15:52 ` Richard Palethorpe
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=Y/zMBSx4p3gqRC3J@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
--cc=wegao@suse.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