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: Tue, 3 Apr 2007 21:04:59 -0700 From: "Paul Menage" <menage@...gle.com> To: vatsa@...ibm.com Cc: sekharan@...ibm.com, ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org, xemul@...ru, containers@...ts.osdl.org, pj@....com, "Eric W. Biederman" <ebiederm@...ssion.com>, mbligh@...gle.com, winget@...gle.com, rohitseth@...gle.com, "Serge E. Hallyn" <serue@...ibm.com>, dev@...ru, devel@...nvz.org Subject: Re: [ckrm-tech] [PATCH 7/7] containers (V7): Container interface to nsproxy subsystem On 4/3/07, Srivatsa Vaddagiri <vatsa@...ibm.com> wrote: > User space queries like "what is the cpuset to which this task belongs", > where the answer needs to be something of the form "/dev/cpuset/C1"? > The patches address that requirement atm by having a dentry pointer in > struct cpuset itself. Have you posted the cpuset implementation over your system yet? The drawback to that is that every subsystem has to add a dentry to its state, and handle the processing. > > Do you see similar queries coming in for every resource controller object > (show me the path of cpu_acct, cpu_ctl, rss_ctl ... objects to which this > task belongs)? IMO that will not be the case, in which case we can avoid > adding N pointers (N = max hierarchies) in nsproxy just to support queries of > those sort. OK, I see your argument that putting it in the aggregator probably isn't the best thing to do from a space point of view in the case when the number of aggregators This seems like a place where my container_subsys_state object is useful - it can store a pointer to the container object (and be maintained by the generic container system), at a space cost of 1 pointer per subsystem grouping, rather than N pointers per aggregator. 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