[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f11576a0804070516r185bff87t449c315bd7787c7e@mail.gmail.com>
Date: Mon, 7 Apr 2008 21:16:39 +0900
From: "KOSAKI Motohiro" <m-kosaki@...es.dti.ne.jp>
To: balbir@...ux.vnet.ibm.com
Cc: "Andi Kleen" <andi@...stfloor.org>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"YAMAMOTO Takashi" <yamamoto@...inux.co.jp>,
"Paul Menage" <menage@...gle.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, "Pavel Emelianov" <xemul@...nvz.org>,
hugh@...itas.com,
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [-mm] Disable the memory controller by default
> 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}
e.g.
user specified cgroup_enable=mem.
if default value is disable, it mean turn to enable.
if default value is enable, it is meaningless param.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists