| 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: <4619EF43.3020104@sw.ru> Date: Mon, 09 Apr 2007 11:46:11 +0400 From: Pavel Emelianov <xemul@...ru> To: menage@...gle.com CC: akpm@...ux-foundation.org, sekharan@...ibm.com, dev@...ru, serue@...ibm.com, vatsa@...ibm.com, ebiederm@...ssion.com, ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org, containers@...ts.osdl.org, mbligh@...gle.com, rohitseth@...gle.com, devel@...nvz.org Subject: Re: [PATCH 6/7] Containers (V8): BeanCounters over generic process containers menage@...gle.com wrote: > This patch implements the BeanCounter resource control abstraction > over generic process containers. It contains the beancounter core > code, plus the numfiles resource counter. It doesn't currently contain > any of the memory tracking code or the code for switching beancounter > context in interrupts. > > Currently all the beancounters resource counters are lumped into a > single hierarchy; ideally it would be possible for each resource > counter to be a separate container subsystem, allowing them to be > connected to different hierarchies. Thanks for your attention, but since we have decided to build a "new" resource controllers above your containers infrastructure, I think there is no need in further BC code porting. Thanks, Pavel. - 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