| 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
| ||
|
Message-ID: <6599ad830706090107u63b7e8c2p8e5c65778cde7473@mail.gmail.com> Date: Sat, 9 Jun 2007 01:07:53 -0700 From: "Paul Menage" <menage@...gle.com> To: "Andrew Morton" <akpm@...ux-foundation.org> Cc: "Balbir Singh" <balbir@...ux.vnet.ibm.com>, "Linux Containers" <containers@...ts.osdl.org>, "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>, "Pavel Emelianov" <xemul@...nvz.org> Subject: Re: [0/1] [patch -mm] Add containerstats (v3) On 6/9/07, Andrew Morton <akpm@...ux-foundation.org> wrote: > > - CONTAINER_DEBUG should depend on CONTAINERS CONTAINER_DEBUG is actually a container subsystem whose sole purpose is to provide debugging information about any hierarchy that it's mounted as a part of. So in some senses it's in the same boat as something like cpusets or the RSS controller. CONFIG_CONTAINER_DEBUG doesn't affect any of the container framework code. > > - the CPUSETS && SMP is weird and should be deleted, unless I'm missing > something Cpusets depends on SMP in the vanilla tree, so that's not anything new that I added. > > - CONTAINERS should depend on CPUSETS You mean the other way around? > > - That leaves CONTAINER_CPUACCT. Really, CONTAINER_CPUACCT should have the same relationship to CONTAINERS as CPUSETS does. Paul - 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/
Powered by blists - more mailing lists