[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47FA10BB.9000305@linux.vnet.ibm.com>
Date: Mon, 07 Apr 2008 17:46:59 +0530
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: KOSAKI Motohiro <m-kosaki@...es.dti.ne.jp>
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
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
--
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