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
| ||
|
Date: Thu, 22 Mar 2007 20:26:49 +0530 From: Srivatsa Vaddagiri <vatsa@...ibm.com> To: "Serge E. Hallyn" <serue@...ibm.com> Cc: Paul Menage <menage@...gle.com>, ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org, xemul@...ru, pj@....com, Sam Vilain <sam@...ain.net>, "Eric W. Biederman" <ebiederm@...ssion.com>, winget@...gle.com, containers@...ts.osdl.org, akpm@...ux-foundation.org, dev@...ru Subject: Re: [ckrm-tech] [PATCH 0/2] resource control file system - aka containers on top of nsproxy! On Thu, Mar 22, 2007 at 09:39:09AM -0500, Serge E. Hallyn wrote: > > What troubles will mounting both cpuset and ns in the same hierarchy > > cause? > > Wow, don't recall the full context here. Sorry to have come back so late on this :) > But at least with Paul's container patchset, a subsystem can only be mounted > once. So if the nsproxy container subsystem is always mounted by itself, > then you cannot remount it to bind it with cpusets. Sure ..I was thinking of mounting both ns and cpuset in same hierarchy for first time itself. -- 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/
Powered by blists - more mailing lists