From: Zefan Li <lizefan@huawei.com>
To: Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>
Cc: <cgroups@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel-team@fb.com>
Subject: Re: [PATCH 1/2] cgroup: clean up the kernel configuration menu nomenclature
Date: Fri, 18 Dec 2015 10:23:03 +0800 [thread overview]
Message-ID: <56736E07.4000300@huawei.com> (raw)
In-Reply-To: <1450390797-4748-2-git-send-email-hannes@cmpxchg.org>
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@cmpxchg.org>
> ---
> 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.
next prev parent reply other threads:[~2015-12-18 2:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 22:19 [PAtCh 0/2] cgroup: prepare kernel config for cgroup2 Johannes Weiner
2015-12-17 22:19 ` [PATCH 1/2] cgroup: clean up the kernel configuration menu nomenclature Johannes Weiner
2015-12-18 2:23 ` Zefan Li [this message]
2015-12-18 16:19 ` Johannes Weiner
2015-12-18 17:39 ` Tejun Heo
2015-12-17 22:19 ` [PATCH 2/2] cgroup: put controller Kconfig options in meaningful order Johannes Weiner
2015-12-18 2:26 ` Zefan Li
2015-12-18 17:45 ` Tejun Heo
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=56736E07.4000300@huawei.com \
--to=lizefan@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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
Powered by JetHome