On Wed, Mar 07, 2007 at 05:35:58PM -0800, Paul Menage wrote: > On 3/7/07, Eric W. Biederman <[EMAIL PROTECTED]> 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).
we (Linux-VServer) call that resource accounting, and it is the first step to resource 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?) ATM, yes, and there is no real harm in doing so this would be a problem for resource containers, unless they are strict hierarchical, i.e. only allow to further restrict the existing resources (which might cause some trouble if existing limits have to be changed at some point) best, Herbert > Paul > _______________________________________________ > Containers mailing list > [EMAIL PROTECTED] > https://lists.osdl.org/mailman/listinfo/containers ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
