From: Tejun Heo <tj@kernel.org>
To: Roman Gushchin <guro@fb.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
cgroups@vger.kernel.org
Subject: Re: [PATCH v2 2/2] cgroup: export list of cgroups v2 features using sysfs
Date: Mon, 6 Nov 2017 12:02:31 -0800 [thread overview]
Message-ID: <20171106200231.GF3252168@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20171106183029.21297-2-guro@fb.com>
On Mon, Nov 06, 2017 at 01:30:29PM -0500, Roman Gushchin wrote:
> The active development of cgroups v2 sometimes leads to a creation
> of interfaces, which are not turned on by default (to provide
> backward compatibility). It's handy to know from userspace, which
> cgroup v2 features are supported without calculating it based
> on the kernel version. So, let's export the list of such features
> using /sys/kernel/cgroup/features pseudo-file.
>
> The list is hardcoded and has to be extended when new functionality
> is added. Each feature is printed on a new line.
>
> Example:
> $ cat /sys/kernel/cgroup/features
> nsdelegate
>
> Signed-off-by: Roman Gushchin <guro@fb.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: kernel-team@fb.com
Applied 1-2 to cgroup/for-4.15.
Thanks.
--
tejun
prev parent reply other threads:[~2017-11-06 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 17:46 [PATCH 1/2] cgroup: export list of delegatable control files using sysfs Roman Gushchin
2017-11-03 17:46 ` [PATCH 2/2] cgroup: export list of cgroups v2 features " Roman Gushchin
2017-11-03 17:56 ` [PATCH 1/2] cgroup: export list of delegatable control files " Tejun Heo
2017-11-06 17:38 ` Tejun Heo
2017-11-06 18:30 ` [PATCH v2 " Roman Gushchin
2017-11-06 18:30 ` [PATCH v2 2/2] cgroup: export list of cgroups v2 features " Roman Gushchin
2017-11-06 20:02 ` Tejun Heo [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=20171106200231.GF3252168@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox