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, 22 Aug 2006 11:43:50 +0400 From: "Pavel V. Emelianov" <xemul@...ru> To: rohitseth@...gle.com CC: Kirill Korotaev <dev@...ru>, Rik van Riel <riel@...hat.com>, ckrm-tech@...ts.sourceforge.net, Dave Hansen <haveblue@...ibm.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Andi Kleen <ak@...e.de>, Christoph Hellwig <hch@...radead.org>, Andrey Savochkin <saw@...ru>, devel@...nvz.org, hugh@...itas.com, Ingo Molnar <mingo@...e.hu>, Alan Cox <alan@...rguk.ukuu.org.uk>, Pavel Emelianov <xemul@...nvz.org> Subject: Re: [ckrm-tech] [RFC][PATCH 5/7] UBC: kernel memory accounting (core) Rohit Seth wrote: [snip] >>>> inodes can belong to multiple containers and so do the pages. >>>> >>> >>> I'm still thinking that inodes should belong to one container (or may be >>> have it configurable based on some flag). >> this is not true for OpenVZ nor Linux-VServer. > > > Well, it is still useful. Just like an anonymous page get charged to > container where the object (task) belong to, file page seems appropriate > to belong to container where the object (inode) belongs to. > > -rohit Making inodes belong to one container only significantly shrinks container density. Sharing of glibc only saves up to 4Mb per container. For the case of 100 containers it is 400Mb of booth - the disk space and (what is more important) - RAM. 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