On Wed, 01 Feb 2006 17:26:00 -0800 chandra seetharaman <[EMAIL PROTECTED]> wrote:
> > > - what is the plan to support "limit" ? > > > > To be honest, I don't have any specific idea to support "limit" currently. > > Probably the userspace daemon that enlarge "guarantee" to the specified > > "limit" might support the "limit", because "guarantee" in the pzone based > > memory resource controller also works as "limit". > > I am not able to visualize how this will work. > > In simple terms, sum of guarantees should _not_ exceed the amount of > available memory but, sum of limits _can_ exceed the amount of available > memory. As far as i understand your implementation, guarantee is > translated to present_pages of the pseudo zone (and is subtracted from > paren't present_pages). How can one set limit to be same as guarantee ? The number of pages in the pseudo zones can also be considered as limit because tasks in a class can't allocate beyond the number of the pages that are allocated to the pseudo zones. > > > - can you provide more information in stats ? > > > > Ok, I'll do that. > > > > > - is it designed to work with cpumeter alone (i.e without ckrm) ? > > > > Maybe it works with cpumeter. > > have you tested it without ckrm (i mean only with cpumeter) The patches I had sent don't include a harness to cpumeter, so we can't run with cpumeter. I suppose we need little work for modifying mm/mem_rc_pzone.c to work with cpumeter because the file was originally written for cpumeter. -- KUROSAWA, Takahiro ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
