[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A25C99B.40303@cn.fujitsu.com>
Date: Wed, 03 Jun 2009 08:53:47 +0800
From: Li Zefan <lizf@...fujitsu.com>
To: Dhaval Giani <dhaval@...ux.vnet.ibm.com>
CC: Paul Menage <menage@...gle.com>, akpm@...ux-foundation.org,
mm-commits@...r.kernel.org, balbir@...ux.vnet.ibm.com,
kamezawa.hiroyu@...fujitsu.com,
lkml <linux-kernel@...r.kernel.org>,
Bharata B Rao <bharata@...ux.vnet.ibm.com>,
libcg-devel <libcg-devel@...ts.sourceforge.net>
Subject: Re: + cgroups-forbid-noprefix-if-mounting-more-than-just-cpuset-subsystem.
patch added to -mm tree
Dhaval Giani wrote:
> 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@...ux.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.
>
I don't think we need to support noprefix in libcgroup.
Even if we decide to support noprefix in the lib, it shouldn't be harder
to handle noprefix+cpuset only than handle noprefix+any combination of
subsystems.
--
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