From: Andrew Morton <akpm@linux-foundation.org>
To: vatsa@linux.vnet.ibm.com
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, containers@lists.osdl.org,
ckrm-tech@lists.sourceforge.net, dhaval@linux.vnet.ibm.com
Subject: Re: [PATCH] Hookup group-scheduler with task container infrastructure
Date: Mon, 10 Sep 2007 10:22:59 -0700 [thread overview]
Message-ID: <20070910102259.dc45a481.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070910172334.GB19100@linux.vnet.ibm.com>
On Mon, 10 Sep 2007 22:53:34 +0530 Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> wrote:
> On Mon, Sep 10, 2007 at 07:05:00PM +0200, Jan Engelhardt wrote:
> > On Sep 10 2007 22:40, Srivatsa Vaddagiri wrote:
> > >+#ifdef CONFIG_FAIR_GROUP_SCHED
> > >+SUBSYS(cpuctlr)
> > >+#endif
> >
> > cpuctl, cpuctrl, cpu_controller?
>
> *shrug* .. I used "cpuctlr" to mean "CPU Controller". Any other short names
> would do. From your list, cpuctl or cpuctrl both qualifies IMO!
>
> Unless folks have strong objection to it, I prefer "cptctlr", the way it is.
>
objection ;) "cpuctlr" isn't memorable. Kernel code is write-rarely,
read-often. "cpu_controller", please. The extra typing is worth it ;)
next prev parent reply other threads:[~2007-09-10 17:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 17:10 [PATCH] Hookup group-scheduler with task container infrastructure Srivatsa Vaddagiri
2007-09-10 17:05 ` Jan Engelhardt
2007-09-10 17:23 ` Srivatsa Vaddagiri
2007-09-10 17:22 ` Andrew Morton [this message]
2007-09-10 17:41 ` Jan Engelhardt
2007-09-10 17:46 ` Srivatsa Vaddagiri
2007-09-10 22:28 ` Dmitry Adamushko
2007-09-11 4:41 ` Srivatsa Vaddagiri
2007-09-11 9:53 ` Dmitry Adamushko
2007-09-12 11:42 ` Srivatsa Vaddagiri
2007-09-12 12:10 ` Srivatsa Vaddagiri
2007-09-12 16:25 ` Dmitry Adamushko
2007-09-13 12:33 ` Srivatsa Vaddagiri
2007-09-14 9:41 ` Ingo Molnar
2007-09-14 15:59 ` Srivatsa Vaddagiri
2007-09-14 16:22 ` Srivatsa Vaddagiri
2007-09-10 22:37 ` Dmitry Adamushko
2007-09-10 22:45 ` Paul Menage
2007-09-11 7:20 ` Cedric Le Goater
2007-09-11 15:22 ` Randy Dunlap
2007-09-11 15:37 ` Jan Engelhardt
2007-09-11 15:51 ` Srivatsa Vaddagiri
2007-09-11 15:53 ` Randy Dunlap
2007-09-11 15:44 ` Paul Menage
2007-09-10 17:28 ` Srivatsa Vaddagiri
2007-09-10 17:42 ` Jan Engelhardt
2007-09-10 18:38 ` [Devel] " Paul Menage
2007-09-11 4:44 ` Srivatsa Vaddagiri
2007-09-18 8:19 ` KAMEZAWA Hiroyuki
2007-09-18 10:44 ` Srivatsa Vaddagiri
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=20070910102259.dc45a481.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=containers@lists.osdl.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.com \
/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