From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
nishimura@mxp.nes.nec.co.jp
Subject: Re: memcg: Fix init/Kconfig documentation
Date: Tue, 21 Oct 2008 15:11:05 +0900 [thread overview]
Message-ID: <20081021151105.f13ec6d2.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20081021055118.GA11429@balbir.in.ibm.com>
On Tue, 21 Oct 2008 11:21:18 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> From: Balbir Singh <balbir@linux.vnet.ibm.com>
> Date: Tue, 21 Oct 2008 11:12:45 +0530
> Subject: [PATCH] memcg: Update Kconfig to remove the struct page overhead statement.
>
> 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.
>
Oh, this is my version..could you merge if this includes something good ?
==
Fixes menu help text for memcg-allocate-page-cgroup-at-boot.patch.
Signed-off-by: KAMEZAWA hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
init/Kconfig | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
Index: mmotm-2.6.27+/init/Kconfig
===================================================================
--- mmotm-2.6.27+.orig/init/Kconfig
+++ mmotm-2.6.27+/init/Kconfig
@@ -401,16 +401,20 @@ config CGROUP_MEM_RES_CTLR
depends on CGROUPS && RESOURCE_COUNTERS
select MM_OWNER
help
- Provides a memory resource controller that manages both page cache and
- RSS memory.
+ Provides a memory resource controller that manages both anonymous
+ memory and page cache. (See Documentation/controllers/memory.txt)
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.
+ associated with each page of memory in the system. By this,
+ 20(40)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
+ usage tracking struct at boot. Total amount of this is printed out
+ at boot.
Only enable when you're ok with these trade offs and really
- sure you need the memory resource controller.
+ sure you need the memory resource controller. Even when you enable
+ this, you can set "cgroup_disable=memory" at your boot option to
+ disable memory resource controller and you can avoid almost all bads.
+ (and lost benefits of memory resource contoller)
This config option also selects MM_OWNER config option, which
could in turn add some fork/exit overhead.
--
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-10-21 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 5:51 memcg: Fix init/Kconfig documentation, [PATCH] memcg: Update Kconfig to remove the struct page overhead statement Balbir Singh, Balbir Singh
2008-10-21 6:11 ` KAMEZAWA Hiroyuki [this message]
2008-10-21 6:16 ` memcg: Fix init/Kconfig documentation 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=20081021151105.f13ec6d2.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.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