On 11/10/06, Arjan van de Ven <[EMAIL PROTECTED]> wrote: > On Fri, 2006-11-10 at 01:06 +0530, Balbir Singh wrote: > > > > Reclaim memory as we hit the max_shares limit. The code for reclamation > > is inspired from Dave Hansen's challenged memory controller and from the > > shrink_all_memory() code > > > Hmm.. I seem to remember that all previous RSS rlimit attempts actually > fell flat on their face because of the reclaim-on-rss-overflow behavior; > in the shared page / cached page (equally important!) case, it means > process A (or container A) suddenly penalizes process B (or container B) > by making B have pagecache misses because A was using a low RSS limit. > > Unmapping the page makes sense, sure, and even moving then to inactive > lists or whatever that is called in the vm today, but reclaim... that's > expensive... >
I see your point, one of things we could do is that we could track shared and cached pages separately and not be so severe on them. I'll play around with this idea and see what I come up with. Thanks for the feedback, Balbir ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
