From: "Paul Menage" <menage@google.com>
To: balbir@linux.vnet.ibm.com
Cc: KOSAKI Motohiro <m-kosaki@ceres.dti.ne.jp>,
Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
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, 7 Apr 2008 10:48:23 -0700 [thread overview]
Message-ID: <6599ad830804071048u5e0687dfy4313467fd95dab1c@mail.gmail.com> (raw)
In-Reply-To: <47FA10BB.9000305@linux.vnet.ibm.com>
On Mon, Apr 7, 2008 at 5:16 AM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> 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.
I don't think we need to guard against that. It seems perfectly valid
to have a lilo config with
append="cgroup_disable=memory"
and then want to boot with the memory controller enabled you can do
lilo -R <image> cgroup_enable=memory
The kernel command line will then look like
"... cgroup_disable=memory cgroup_enable=memory"
and the last switch should win.
Paul
next prev parent reply other threads:[~2008-04-07 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 11:51 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
2008-04-07 17:48 ` Paul Menage [this message]
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=6599ad830804071048u5e0687dfy4313467fd95dab1c@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=balbir@linux.vnet.ibm.com \
--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=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