OpenVZ Forum - RDF feed
type: channel
items: [PATCH] Memory controller Add Documentation
items: Re: [PATCH] Memory controller Add Documentation

[PATCH] Memory controller Add Documentation
type: item
description: Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com> --- Documentation/memcontrol.txt | 193 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 193 insertions(+) diff -puN /dev/null Documentation/memcontrol.txt --- /dev/null 2007-06-01 20:42:04.000000000 +0530 +++ linux-2.6.23-rc2-mm2-balbir/Documentation/memcontrol.txt 2007-08-22 18:29:29.000000000 +0530 @@ -0,0 +1,193 @@ +Memory Controller + +0. Salient features + +a. Enable control of both RSS and Page Cache pages +b. The infrastructures allows easy addition of other types of memory to control +c. Provides *zero overhead* for non memory controller users +d. Provides a double LRU, global memory pressure causes reclaim from the + global LRU, a container on hitting a limit, reclaims from the per + container LRU + +1. History + +The memory controller has a long history. A request for comments for the memory +controller was posted by Balbir Singh [1]. At the time the RFC was posted +there were several implementations for memory control, the goal of the +RFC was to build consensus and agreement for the minimal features required +for memory control. The first RSS controller was posted by Balbir Singh[2] +in Feb 2007. Pavel Emelianov [3][4][5] has since posted three versions of the +RSS controller. At OLS, at the resource management BoF, everyone suggested +that we handle both page cache and RSS together. Another request was raised +to allow user space handling of OOM. The current memory controller is +at version 6, it combines both RSS and Page Cache Control [11]. + +2. Memory Control + +Memory is a unique resource in the sense that it is present in a limited +amount. If a task requires a lot of CPU processing, the task can spread +its processing over a period of hours, days, months or years, but with +memory, the same physical memory needs to be reused to accomplish the task. + +The memory controller implementation has been divided into phases, these +are + +1. Memory controller +2. mlock(2) controller +3. K…
creator: Balbir Singh
date: 2007-08-22T13:06:12-00:00

Re: [PATCH] Memory controller Add Documentation
type: item
description: Thank you for documentaion. How about adding following topics ? - Benefit and Purpose. When this function help a user. - What is accounted as RSS. - What is accounted as page-cache. - What are not accoutned now. - When a page is accounted (charged.) - about mem_control_type - When a user can remove memory controller with no tasks (by rmdir) and What happens if a user does. - What happens when a user migrates a task to other container. Writing all above may be too much :) I'm sorry if I say something pointless. Thanks, -Kame On Wed, 22 Aug 2007 18:36:12 +0530 Balbir Singh <balbir@linux.vnet.ibm.com> wrote: > > > Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com> > --- > > Documentation/memcontrol.txt | 193 +++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 193 insertions(+) > > diff -puN /dev/null Documentation/memcontrol.txt > --- /dev/null 2007-06-01 20:42:04.000000000 +0530 > +++ linux-2.6.23-rc2-mm2-balbir/Documentation/memcontrol.txt 2007-08-22 18:29:29.000000000 +0530 > @@ -0,0 +1,193 @@ > +Memory Controller > + > +0. Salient features > + > +a. Enable control of both RSS and Page Cache pages > +b. The infrastructures allows easy addition of other types of memory to control > +c. Provides *zero overhead* for non memory controller users > +d. Provides a double LRU, global memory pressure causes reclaim from the > + global LRU, a container on hitting a limit, reclaims from the per > + container LRU > + > +1. History > + > +The memory controller has a long history. A request for comments for the memory > +controller was posted by Balbir Singh [1]. At the time the RFC was posted > +there were several implementations for memory control, the goal of the > +RFC was to build consensus and agreement for the minimal features required > +for memory control. The first RSS controller was posted by Balbir Singh[2] > +in Feb 2007. Pavel Emelianov [3][4][5] has since posted three versions of the > +RSS controller. At OLS, at the resource management BoF, everyone…
creator: KAMEZAWA Hiroyuki
date: 2007-08-23T08:36:21-00:00

Re: [PATCH] Memory controller Add Documentation
type: item
description: KAMEZAWA Hiroyuki wrote: > Thank you for documentaion. How about adding following topics ? > > - Benefit and Purpose. When this function help a user. > - What is accounted as RSS. > - What is accounted as page-cache. > - What are not accoutned now. > - When a page is accounted (charged.) > - about mem_control_type > - When a user can remove memory controller with no tasks (by rmdir) > and What happens if a user does. > - What happens when a user migrates a task to other container. > Thanks for your input. I'll try and incorporate your comments into the documentation (I think it will help developers and users alike). > Writing all above may be too much :) > > I'm sorry if I say something pointless. > No.. not at all! Thank you for reading the documentation and commenting on it. > Thanks, > -Kame > > -- Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: Balbir Singh
date: 2007-08-23T08:38:37-00:00

Re: [PATCH] Memory controller Add Documentation
type: item
description: > +echo 1 > /proc/sys/vm/drop_pages will help get rid of some of the pages > +cached in the container (page cache pages). drop_caches YAMAMOTO Takashi _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: yamamoto
date: 2007-08-24T08:48:15-00:00