| 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: <6599ad830703071735m222e26b7v47a54ca0aaffd902@mail.gmail.com> Date: Wed, 7 Mar 2007 17:35:58 -0800 From: "Paul Menage" <menage@...gle.com> To: "Eric W. Biederman" <ebiederm@...ssion.com> Cc: "Sam Vilain" <sam@...ain.net>, "Srivatsa Vaddagiri" <vatsa@...ibm.com>, ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org, xemul@...ru, dev@...ru, pj@....com, winget@...gle.com, containers@...ts.osdl.org, "Serge E. Hallyn" <serue@...ibm.com>, akpm@...ux-foundation.org Subject: Re: [ckrm-tech] [PATCH 0/2] resource control file system - aka containers on top of nsproxy! On 3/7/07, Eric W. Biederman <ebiederm@...ssion.com> wrote: > Pretty much. For most of the other cases I think we are safe referring > to them as resource controls or resource limits. I know that roughly covers > what cpusets and beancounters and ckrm currently do. Plus resource monitoring (which may often be a subset of resource control/limits). > > 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. That's going to to be the case for most resource controllers - is that the case for namespaces? (e.g. can any task unshare say its mount namespace?) 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