From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KOSAKI Motohiro <m-kosaki@ceres.dti.ne.jp>
Cc: Andi Kleen <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,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [-mm] Disable the memory controller by default
Date: Mon, 07 Apr 2008 17:46:59 +0530 [thread overview]
Message-ID: <47FA10BB.9000305@linux.vnet.ibm.com> (raw)
In-Reply-To: <2f11576a0804070516r185bff87t449c315bd7787c7e@mail.gmail.com>
KOSAKI Motohiro wrote:
>> The boot control options apply to all controllers and we want to allow
>> controllers to decide whether they should be turned on or off. With sufficient
>> documentation support in Documentation/kernel-parameters.txt, don't you think we
>> can expect this to work as the user intended?
>
> 2 parameter is wrong?
>
> cgroup_disable= [KNL] Disable a particular controller
> Format: {name of the controller(s) to disable}
> cgroup_enable= [KNL] Enable a particular controller
> Format: {name of the controller(s) to enable}
>
No, it is not all bad. That can be done, but we need to guard against a usage like
cgroup_disable=memory cgroup_enable=memory
The user will probably get what he/she deserves for it.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2008-04-07 12:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 11:51 [-mm] Disable the memory controller by default Balbir Singh
2008-04-07 12:03 ` Andi Kleen
2008-04-07 12:03 ` Balbir Singh
2008-04-07 12:16 ` Andi Kleen
2008-04-07 12:16 ` KOSAKI Motohiro
2008-04-07 12:16 ` Balbir Singh [this message]
2008-04-07 17:48 ` Paul Menage
2008-04-07 12:12 ` KOSAKI Motohiro
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=47FA10BB.9000305@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=m-kosaki@ceres.dti.ne.jp \
--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.