Linux cgroups development
 help / color / mirror / Atom feed
From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	kernel-team-b10kYP2dOMg@public.gmane.org
Subject: Re: [PATCH 1/2] cgroup: clean up the kernel configuration menu nomenclature
Date: Fri, 18 Dec 2015 12:39:23 -0500	[thread overview]
Message-ID: <20151218173923.GK4026@mtj.duckdns.org> (raw)
In-Reply-To: <56736E07.4000300-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>

On Fri, Dec 18, 2015 at 10:23:03AM +0800, Zefan Li wrote:
> >  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.

I think it's fine to call all of them controllers.  Let's use that as
the external facing noun to call all cgroup subsystems.  It is a lot
more specific and better describes the main purpose.

Thanks.

-- 
tejun

  parent reply	other threads:[~2015-12-18 17:39 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
     [not found]   ` <1450390797-4748-2-git-send-email-hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2015-12-18  2:23     ` Zefan Li
     [not found]       ` <56736E07.4000300-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-12-18 16:19         ` Johannes Weiner
2015-12-18 17:39         ` Tejun Heo [this message]
2015-12-17 22:19 ` [PATCH 2/2] cgroup: put controller Kconfig options in meaningful order Johannes Weiner
     [not found]   ` <1450390797-4748-3-git-send-email-hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
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=20151218173923.GK4026@mtj.duckdns.org \
    --to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
    --cc=kernel-team-b10kYP2dOMg@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.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