[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56736EBD.8060302@huawei.com>
Date: Fri, 18 Dec 2015 10:26:05 +0800
From: Zefan Li <lizefan@...wei.com>
To: Johannes Weiner <hannes@...xchg.org>, Tejun Heo <tj@...nel.org>
CC: <cgroups@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<kernel-team@...com>
Subject: Re: [PATCH 2/2] cgroup: put controller Kconfig options in meaningful
order
On 2015/12/18 6:19, Johannes Weiner wrote:
> To make it easier to quickly find what's needed list the basic
> resource controllers of cgroup2 first - io, memory, cpu - while
> pushing the more exotic and/or legacy controllers to the bottom.
>
> Signed-off-by: Johannes Weiner <hannes@...xchg.org>
Acked-by: Zefan Li <lizefan@...wei.com>
> ---
> init/Kconfig | 214 +++++++++++++++++++++++++++++------------------------------
> 1 file changed, 107 insertions(+), 107 deletions(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index ed324f5..fdb5ecb 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -957,64 +957,6 @@ menuconfig CGROUPS
>
...
> +config CGROUP_PERF
> + bool "Perf controller"
> + depends on PERF_EVENTS && CGROUPS
While you are at it, remove "&& CGROUPS" ?
> + help
> + This option extends the perf per-cpu mode to restrict monitoring
> + to threads which belong to the cgroup specified and run on the
> + designated cpu.
> +
> + Say N if unsure.
> +
> +config CGROUP_DEBUG
> + bool "Example controller"
> default n
> - ---help---
> - Enable some debugging help. Currently it exports additional stat
> - files in a cgroup which can be useful for debugging.
> + help
> + This option enables a simple controller that exports
> + debugging information about the cgroups framework.
>
> -config CGROUP_WRITEBACK
> - bool
> - depends on MEMCG && BLK_CGROUP
> - default y
> + Say N.
>
> endif # CGROUPS
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists