| 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: Mon, 30 Oct 2006 23:37:44 +0530 From: Balbir Singh <balbir@...ibm.com> To: balbir@...ibm.com CC: Pavel Emelianov <xemul@...nvz.org>, vatsa@...ibm.com, dev@...nvz.org, sekharan@...ibm.com, ckrm-tech@...ts.sourceforge.net, haveblue@...ibm.com, linux-kernel@...r.kernel.org, pj@....com, matthltc@...ibm.com, dipankar@...ibm.com, rohitseth@...gle.com, menage@...gle.com, linux-mm@...ck.org Subject: Re: [ckrm-tech] RFC: Memory Controller Balbir Singh wrote: [snip] > >> I see that everyone agree that we want to see three resources: >> 1. kernel memory >> 2. unreclaimable memory >> 3. reclaimable memory >> if this is right then let's save it somewhere >> (e.g. http://wiki.openvz.org/Containers/UBC_discussion) >> and go on discussing the next question - interface. > > I understand that kernel memory accounting is the first priority for > containers, but accounting kernel memory requires too many changes > to the VM core, hence I was hesitant to put it up as first priority. > > But in general I agree, these are the three important resources for > accounting and control I missed out to mention, I hope you were including the page cache in your definition of reclaimable memory. > > [snip] > -- Balbir Singh, Linux Technology Center, IBM Software Labs - 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