From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: andi@firstfloor.org, Andrew Morton <akpm@linux-foundation.org>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
Paul Menage <menage@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Pavel Emelianov <xemul@openvz.org>,
hugh@veritas.com
Subject: Re: [-mm] Disable the memory controller by default (v2)
Date: Tue, 08 Apr 2008 08:01:21 +0530 [thread overview]
Message-ID: <47FAD8F9.7070308@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080408100902.fcd9d911.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki wrote:
> On Mon, 07 Apr 2008 18:32:15 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>
>>
>> Changelog v1
>>
>> 1. Split cgroup_disable into cgroup_disable and cgroup_enable
>> 2. Remove cgroup_toggle
>>
>> Due to the overhead of the memory controller. The
>> memory controller is now disabled by default. This patch adds cgroup_enable.
>>
>> If everyone agrees on this approach and likes it, should we push this
>> into 2.6.25?
>>
>> Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
>> ---
> BTW, how the user can know which controllers are on/off at default ?
> All controllers are off ?
>
/proc/cgroups has an enabled field (fourth one). That should show what is
enabled/disabled. I've also documented it in
Documentation/kernel-parameters.txt. I intend to enable the memory controller
again, once we bring down the overhead.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
prev parent reply other threads:[~2008-04-08 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 13:02 [-mm] Disable the memory controller by default (v2) Balbir Singh
2008-04-07 13:22 ` KOSAKI Motohiro
2008-04-07 17:43 ` Paul Menage
2008-04-08 1:09 ` KAMEZAWA Hiroyuki
2008-04-08 2:31 ` Balbir Singh [this message]
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=47FAD8F9.7070308@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.