linux-kernel - Re: [PATCH] Hookup group-scheduler with task container infrastructure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 10 Sep 2007 10:22:59 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	vatsa@...ux.vnet.ibm.com
Cc:	Jan Engelhardt <jengelh@...putergmbh.de>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	containers@...ts.osdl.org, ckrm-tech@...ts.sourceforge.net,
	dhaval@...ux.vnet.ibm.com
Subject: Re: [PATCH] Hookup group-scheduler with task container
 infrastructure

On Mon, 10 Sep 2007 22:53:34 +0530 Srivatsa Vaddagiri <vatsa@...ux.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 ;)
-
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/