From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
lizf@cn.fujitsu.com, balbir@linux.vnet.ibm.com,
kamezawa.hiroyu@jp.fujitsu.com,
lkml <linux-kernel@vger.kernel.org>,
Bharata B Rao <bharata@linux.vnet.ibm.com>,
libcg-devel <libcg-devel@lists.sourceforge.net>
Subject: Re: + cgroups-forbid-noprefix-if-mounting-more-than-just-cpuset-subsystem. patch added to -mm tree
Date: Tue, 2 Jun 2009 23:10:42 +0530 [thread overview]
Message-ID: <20090602174042.GD16753@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830906020908s7cb6afe6pd83ca35b82d148a4@mail.gmail.com>
On Tue, Jun 02, 2009 at 09:08:04AM -0700, Paul Menage wrote:
> On Tue, Jun 2, 2009 at 2:09 AM, Dhaval Giani <dhaval@linux.vnet.ibm.com> wrote:
> >
> > I am not sure if this is a good idea. For libcgroup, we would then be
> > adding a special case for just cpuset. I would rather that we allow it
> > either for all the subsystems or none of them.
> >
>
> libcgroup shouldn't be using the noprefix option. Its only intentded
> use is to allow the legacy "cpuset" filesystem type to be mounted and
> to see the same fileset as it had before the cgroups transition.
>
It does not. But if some user is using that option, we need to be in a
position to handle it.
I am quite happy not supporting the noprefix option in the library if it
is fine.
Thanks,
--
regards,
Dhaval
next prev parent reply other threads:[~2009-06-02 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200906020602.n5262wcu008560@imap1.linux-foundation.org>
2009-06-02 9:09 ` + cgroups-forbid-noprefix-if-mounting-more-than-just-cpuset-subsystem. patch added to -mm tree Dhaval Giani
2009-06-02 16:08 ` Paul Menage
2009-06-02 17:40 ` Dhaval Giani [this message]
2009-06-02 20:35 ` Andrew Morton
2009-06-03 0:02 ` KAMEZAWA Hiroyuki
2009-06-03 5:20 ` Dhaval Giani
2009-06-02 23:27 ` Balbir Singh
2009-06-03 0:53 ` 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=20090602174042.GD16753@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=libcg-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=mm-commits@vger.kernel.org \
/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