From: Balbir Singh <balbir@linux.vnet.ibm.com>
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
nishimura@mxp.nes.nec.co.jp
Subject: memcg: Fix init/Kconfig documentation
Subject: [PATCH] memcg: Update Kconfig to remove the struct page overhead statement.
Date: Tue, 21 Oct 2008 11:21:18 +0530 [thread overview]
Date: Tue, 21 Oct 2008 11:12:45 +0530 [thread overview]
Message-ID: <20081021055118.GA11429@balbir.in.ibm.com> (raw)
The memory resource controller no longer has a struct page overhead
associated with it. The init/Kconfig help has been replaced with
something more suitable based on the current implementation.
Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
---
init/Kconfig | 11 ++++-------
1 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/init/Kconfig b/init/Kconfig
index 113c74c..1847f87 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -404,13 +404,10 @@ config CGROUP_MEM_RES_CTLR
Provides a memory resource controller that manages both page cache and
RSS memory.
- Note that setting this option increases fixed memory overhead
- associated with each page of memory in the system by 4/8 bytes
- and also increases cache misses because struct page on many 64bit
- systems will not fit into a single cache line anymore.
-
- Only enable when you're ok with these trade offs and really
- sure you need the memory resource controller.
+ The config option adds a small memory overhead proportional to the
+ size of memory. The controller can be disabled at run time by
+ using the cgroup_disable=memory option, at which point the overhead
+ disappears.
This config option also selects MM_OWNER config option, which
could in turn add some fork/exit overhead.
--
1.5.6.3
Balbir
--
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 reply other threads:[~2008-10-21 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 5:51 Balbir Singh, Balbir Singh [this message]
2008-10-21 6:11 ` KAMEZAWA Hiroyuki
2008-10-21 6:16 ` 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=20081021055118.GA11429@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.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