From: "Paul Menage" <menage@google.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: 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 (v3)
Date: Tue, 8 Apr 2008 07:57:15 -0700 [thread overview]
Message-ID: <6599ad830804080757w7942e4ddtc1381230541613a2@mail.gmail.com> (raw)
In-Reply-To: <20080408114613.8165.69030.sendpatchset@localhost.localdomain>
On Tue, Apr 8, 2008 at 4:46 AM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> 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>
Looks good to me - although I wouldn't bother with the "inline" on
cgroup_turnonoff()
Acked-by: Paul Menage <menage@google.com>
> ---
>
> Documentation/kernel-parameters.txt | 3 +++
> kernel/cgroup.c | 17 +++++++++++++----
> mm/memcontrol.c | 1 +
> 3 files changed, 17 insertions(+), 4 deletions(-)
>
> diff -puN kernel/cgroup.c~memory-controller-default-option-off kernel/cgroup.c
> --- linux-2.6.25-rc8/kernel/cgroup.c~memory-controller-default-option-off 2008-04-07 16:24:28.000000000 +0530
> +++ linux-2.6.25-rc8-balbir/kernel/cgroup.c 2008-04-08 16:04:49.000000000 +0530
> @@ -3063,7 +3063,7 @@ static void cgroup_release_agent(struct
> mutex_unlock(&cgroup_mutex);
> }
>
> -static int __init cgroup_disable(char *str)
> +static inline int __init cgroup_turnonoff(char *str, int disable)
> {
> int i;
> char *token;
> @@ -3076,13 +3076,22 @@ static int __init cgroup_disable(char *s
> struct cgroup_subsys *ss = subsys[i];
>
> if (!strcmp(token, ss->name)) {
> - ss->disabled = 1;
> - printk(KERN_INFO "Disabling %s control group"
> - " subsystem\n", ss->name);
> + ss->disabled = disable;
> break;
> }
> }
> }
> return 1;
> }
> +
> +static int __init cgroup_disable(char *str)
> +{
> + return cgroup_turnonoff(str, 1);
> +}
> __setup("cgroup_disable=", cgroup_disable);
> +
> +static int __init cgroup_enable(char *str)
> +{
> + return cgroup_turnonoff(str, 0);
> +}
> +__setup("cgroup_enable=", cgroup_enable);
> diff -puN mm/memcontrol.c~memory-controller-default-option-off mm/memcontrol.c
> --- linux-2.6.25-rc8/mm/memcontrol.c~memory-controller-default-option-off 2008-04-07 16:24:28.000000000 +0530
> +++ linux-2.6.25-rc8-balbir/mm/memcontrol.c 2008-04-07 16:40:22.000000000 +0530
> @@ -1104,4 +1104,5 @@ struct cgroup_subsys mem_cgroup_subsys =
> .populate = mem_cgroup_populate,
> .attach = mem_cgroup_move_task,
> .early_init = 0,
> + .disabled = 1,
> };
> diff -puN Documentation/kernel-parameters.txt~memory-controller-default-option-off Documentation/kernel-parameters.txt
> --- linux-2.6.25-rc8/Documentation/kernel-parameters.txt~memory-controller-default-option-off 2008-04-07 16:38:25.000000000 +0530
> +++ linux-2.6.25-rc8-balbir/Documentation/kernel-parameters.txt 2008-04-07 17:53:28.000000000 +0530
> @@ -382,8 +382,11 @@ and is between 256 and 4096 characters.
> See Documentation/s390/CommonIO for details.
>
> cgroup_disable= [KNL] Disable a particular controller
> + cgroup_enable= [KNL] Enable a particular controller
> + For both cgroup_enable and cgroup_enable
> Format: {name of the controller(s) to disable}
> {Currently supported controllers - "memory"}
> + {Memory controller is disabled by default}
>
> checkreqprot [SELINUX] Set initial checkreqprot flag value.
> Format: { "0" | "1" }
> _
>
> --
> Warm Regards,
> Balbir Singh
> Linux Technology Center
> IBM, ISTL
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-04-08 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 11:46 Balbir Singh
2008-04-08 14:57 ` Paul Menage [this message]
2008-04-08 23:34 ` KAMEZAWA Hiroyuki
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=6599ad830804080757w7942e4ddtc1381230541613a2@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=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