| 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: <20070309181908.GC21661@in.ibm.com> Date: Fri, 9 Mar 2007 23:49:08 +0530 From: Srivatsa Vaddagiri <vatsa@...ibm.com> To: "Eric W. Biederman" <ebiederm@...ssion.com>, Paul Menage <menage@...gle.com>, ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org, xemul@...ru, pj@....com, winget@...gle.com, containers@...ts.osdl.org, akpm@...ux-foundation.org Subject: Re: [ckrm-tech] [PATCH 0/2] resource control file system - aka containers on top of nsproxy! On Fri, Mar 09, 2007 at 01:53:57AM +0100, Herbert Poetzl wrote: > > The real trick is that I believe these groupings are designed to > > be something you can setup on login and then not be able to switch > > out of. Which means we can't use sessions and process groups as the > > grouping entities as those have different semantics. > > precisely, once you are inside a resource container, you > must not have the ability to modify its limits, and to > some degree, you should not know about the actual available > resources, but only about the artificial limits >From non-container workload management perspective, we do desire dynamic manipulation of limits associated with a group and also the ability to move tasks across resource-classes/groups. -- 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