From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: linux-mm@kvack.org
Cc: Hugh Dickins <hugh@veritas.com>, Paul Menage <menage@google.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Herbert Poetzl <herbert@13thfloor.at>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Emelianov <xemul@openvz.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Rik Van Riel <riel@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: [RFC] [PATCH 4/4] Add soft limit documentation
Date: Wed, 13 Feb 2008 20:42:56 +0530 [thread overview]
Message-ID: <20080213151256.7529.59791.sendpatchset@localhost.localdomain> (raw)
In-Reply-To: <20080213151201.7529.53642.sendpatchset@localhost.localdomain>
Add documentation for the soft limit feature.
Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
---
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
+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.
+
+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
+hard limit.
+
+Example setting of soft limit
+
+# echo -n 100M > memory.soft_limit_in_bytes
+
4. Testing
Balbir posted lmbench, AIM9, LTP and vmmstress results [10] and [11].
_
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-02-13 15:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 15:12 [RFC] [PATCH 0/4] Add soft limits to the memory controller Balbir Singh
2008-02-13 15:12 ` [RFC] [PATCH 1/4] Modify resource counters to add soft limit support Balbir Singh
2008-02-13 17:12 ` Pavel Emelyanov
2008-02-13 17:19 ` Balbir Singh
2008-02-13 17:38 ` Pavel Emelyanov
2008-02-13 17:54 ` Balbir Singh
2008-02-13 15:12 ` [RFC] [PATCH 2/4] Add the soft limit interface Balbir Singh
2008-02-13 15:12 ` [RFC] [PATCH 3/4] Reclaim from groups over their soft limit under memory pressure Balbir Singh
2008-02-14 7:30 ` KAMEZAWA Hiroyuki
2008-02-14 7:40 ` Balbir Singh
2008-02-14 8:42 ` KAMEZAWA Hiroyuki
2008-02-14 9:16 ` Balbir Singh
2008-02-15 4:17 ` Paul Menage
2008-02-15 4:25 ` Balbir Singh
2008-02-15 5:07 ` KAMEZAWA Hiroyuki
2008-02-15 5:16 ` Paul Menage
2008-02-15 5:18 ` Balbir Singh
2008-02-15 5:30 ` Paul Menage
2008-02-15 5:33 ` KAMEZAWA Hiroyuki
2008-02-15 5:29 ` KAMEZAWA Hiroyuki
2008-02-15 6:36 ` Balbir Singh
2008-02-14 10:27 ` YAMAMOTO Takashi
2008-02-15 3:19 ` Balbir Singh
2008-02-13 15:12 ` Balbir Singh [this message]
2008-02-13 15:59 ` [RFC] [PATCH 4/4] Add soft limit documentation Randy Dunlap
2008-02-13 16:08 ` Balbir Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080213151256.7529.59791.sendpatchset@localhost.localdomain \
--to=balbir@linux.vnet.ibm.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=herbert@13thfloor.at \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).