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]

Message-ID: <20070910172334.GB19100@linux.vnet.ibm.com>
Date:	Mon, 10 Sep 2007 22:53:34 +0530
From:	Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Ingo Molnar <mingo@...e.hu>, akpm@...ux-foundation.org,
	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, 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.

-- 
Regards,
vatsa
-
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/