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: Wed, 20 Sep 2006 12:48:41 -0700 (PDT) From: Christoph Lameter <clameter@....com> To: Peter Zijlstra <a.p.zijlstra@...llo.nl> cc: Rohit Seth <rohitseth@...gle.com>, Nick Piggin <nickpiggin@...oo.com.au>, CKRM-Tech <ckrm-tech@...ts.sourceforge.net>, devel@...nvz.org, linux-kernel <linux-kernel@...r.kernel.org>, Linux Memory Management <linux-mm@...ck.org> Subject: Re: [patch00/05]: Containers(V2)- Introduction On Wed, 20 Sep 2006, Peter Zijlstra wrote: > > Which comes naturally with cpusets. > > How are shared mappings dealt with, are pages charged to the set that > first faults them in? They are charged to the node from which they were allocated. If the process is restricted to the node (container) then all pages allocated are are charged to the container regardless if they are shared or not. - 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