Re: [PATCH 1/2] cgroup: clean up the kernel configuration menu nomenclature

[Johannes Weiner]

On Fri, Dec 18, 2015 at 10:23:03AM +0800, Zefan Li wrote:
> On 2015/12/18 6:19, Johannes Weiner wrote:
> >The config options for the different cgroup controllers use various
> >terms: resource controller, cgroup subsystem, etc. Simplify this to
> >"controller", which is clear enough in the cgroup context.
> >
> >Signed-off-by: Johannes Weiner <hannes@xxxxxxxxxxx>
> >---
> >  init/Kconfig | 65 ++++++++++++++++++++++++------------------------------------
> >  1 file changed, 26 insertions(+), 39 deletions(-)
> >
> >diff --git a/init/Kconfig b/init/Kconfig
> >index 16840b4..ed324f5 100644
> >--- a/init/Kconfig
> >+++ b/init/Kconfig
> >@@ -958,23 +958,22 @@ menuconfig CGROUPS
> >  if CGROUPS
> >
> >  config CGROUP_DEBUG
> >-	bool "Example debug cgroup subsystem"
> >+	bool "Example controller"
> 
> But not all cgroup subsystems are controllers, which are debug, perf and
> cpuacct. I'm fine the other changes.

Hm, I basically use the term controller to denote any modular
component of cgroup that is not part of the cgroup core.

Do we need to be more specific/accurate than that? Especially because
there won't be any purely informational modules in cgroup2 anymore,
they'll all actually control some resource or behavior.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/