From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from d28relay02.in.ibm.com (d28relay02.in.ibm.com [9.184.220.59]) by e28smtp01.in.ibm.com (8.13.1/8.13.1) with ESMTP id m1DGBiHr002673 for ; Wed, 13 Feb 2008 21:41:44 +0530 Received: from d28av05.in.ibm.com (d28av05.in.ibm.com [9.184.220.67]) by d28relay02.in.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m1DGBiwI839738 for ; Wed, 13 Feb 2008 21:41:44 +0530 Received: from d28av05.in.ibm.com (loopback [127.0.0.1]) by d28av05.in.ibm.com (8.13.1/8.13.3) with ESMTP id m1DGBhxw028415 for ; Wed, 13 Feb 2008 16:11:44 GMT Message-ID: <47B3161A.9090504@linux.vnet.ibm.com> Date: Wed, 13 Feb 2008 21:38:58 +0530 From: Balbir Singh Reply-To: balbir@linux.vnet.ibm.com MIME-Version: 1.0 Subject: Re: [RFC] [PATCH 4/4] Add soft limit documentation References: <20080213151201.7529.53642.sendpatchset@localhost.localdomain> <20080213151256.7529.59791.sendpatchset@localhost.localdomain> <20080213075929.52a3ae05.randy.dunlap@oracle.com> In-Reply-To: <20080213075929.52a3ae05.randy.dunlap@oracle.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Randy Dunlap Cc: linux-mm@kvack.org, Hugh Dickins , Paul Menage , YAMAMOTO Takashi , Peter Zijlstra , Lee Schermerhorn , Herbert Poetzl , David Rientjes , Andrew Morton , Pavel Emelianov , Nick Piggin , Rik Van Riel , "Eric W. Biederman" , KAMEZAWA Hiroyuki List-ID: Randy Dunlap wrote: > On Wed, 13 Feb 2008 20:42:56 +0530 Balbir Singh wrote: > >> Add documentation for the soft limit feature. >> >> Signed-off-by: Balbir Singh >> --- >> >> Documentation/controllers/memory.txt | 16 ++++++++++++++++ >> 1 file changed, 16 insertions(+) >> >> diff -puN Documentation/controllers/memory.txt~memory-controller-add-soft-limit-documentation Documentation/controllers/memory.txt >> --- linux-2.6.24/Documentation/controllers/memory.txt~memory-controller-add-soft-limit-documentation 2008-02-13 18:45:40.000000000 +0530 >> +++ linux-2.6.24-balbir/Documentation/controllers/memory.txt 2008-02-13 18:49:58.000000000 +0530 >> @@ -201,6 +201,22 @@ The memory.force_empty gives an interfac >> >> will drop all charges in cgroup. Currently, this is maintained for test. >> >> +The file memory.soft_limit_in_bytes allows users to set soft limits. A soft >> +limit is set in a manner similar to limit. The limit feature described >> +earlier is a hard limit, a group can never exceed it's hard limit. A soft > > ; [or: ". A group ..."] Will do > and s/it's/its/ > Thanks, I seem to use it's instead of its at times. I'll double check next time >> +limit on the other hand can be exceeded. A group will be shrunk back >> +to it's soft limit, when there is memory pressure/contention. > > its [it's == it is] > >> + >> +Ideally the soft limit should always be set to a value smaller than the >> +hard limit. However, the code does not force the user to do so. The soft >> +limit can be greater than the hard limit; then the soft limit has >> +no meaning in that setup, since the group will alwasy be restrained to its > > always > Will fix >> +hard limit. >> + >> +Example setting of soft limit >> + >> +# echo -n 100M > memory.soft_limit_in_bytes >> + >> 4. Testing > Thanks for helping us keep the documentation readable. -- Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org