From: David Rientjes <rientjes@google.com>
To: Paul Menage <menage@google.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Emelianov <xemul@openvz.org>,
Hugh Dickins <hugh@veritas.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org,
taka@valinux.co.jp, linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH] Add cgroup support for enabling controllers at boot time
Date: Fri, 7 Mar 2008 00:56:33 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.1.00.0803070055020.3470@chino.kir.corp.google.com> (raw)
In-Reply-To: <6599ad830803070040i5e54f5f3u9b4c753ac5a87771@mail.gmail.com>
On Fri, 7 Mar 2008, Paul Menage wrote:
> > Since the command line is logically delimited by spaces, you can
> > accidently disable a subsystem if its name appears in any of your kernel
> > options following your cgroup_disable= option.
>
> I think that you're confusing this with things like the very early
> memory init setup parameters, which do operate on the raw commandline.
>
> By the time anything is passed to a __setup() function, it's already
> been split into separate strings at space boundaries.
>
Ok, so the cgroup_disable= parameter should be a list of subsystem names
delimited by anything other than a space that the user wants disabled.
That makes more sense, thanks.
--
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-03-07 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 18:59 Balbir Singh
2008-03-06 19:00 ` [PATCH] Make memory resource control aware of boot options Balbir Singh
2008-03-06 19:10 ` [PATCH] Add cgroup support for enabling controllers at boot time David Rientjes
2008-03-07 4:41 ` Balbir Singh
2008-03-07 4:58 ` KAMEZAWA Hiroyuki
2008-03-07 5:15 ` David Rientjes
2008-03-07 5:14 ` David Rientjes
2008-03-07 8:40 ` Paul Menage
2008-03-07 8:56 ` David Rientjes [this message]
2008-03-07 9:01 ` Paul Menage
2008-03-06 19:11 ` Randy Dunlap
2008-03-07 0:05 ` Li Zefan
2008-03-07 4:37 ` Balbir Singh
2008-03-07 0:13 ` Li Zefan
2008-03-07 4:37 ` Balbir Singh
2008-03-07 4:56 ` Li Zefan
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=alpine.DEB.1.00.0803070055020.3470@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.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=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=skumar@linux.vnet.ibm.com \
--cc=taka@valinux.co.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