[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830911041325i9b309a7y4d912d6be7ddbdd9@mail.gmail.com>
Date: Wed, 4 Nov 2009 13:25:46 -0800
From: Paul Menage <menage@...gle.com>
To: Matt Helsley <matthltc@...ibm.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
balbir@...ux.vnet.ibm.com,
Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
containers@...ts.linux-foundation.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jan@...p1.linux-foundation.org,
Bharata B Rao <bharata.rao@...ibm.com>,
libcg-devel <libcg-devel@...ts.sourceforge.net>,
Safranek <jsafrane@...hat.com>
Subject: Re: [RFC] Mount point suggestions for cgroup
On Wed, Nov 4, 2009 at 9:35 AM, Matt Helsley <matthltc@...ibm.com> wrote:
>
> If anything, "standardizing" the mount point(s) will likely provide a false
> sense of uniformity and we'll get some bad userspace scripts/tools that
> break when "nonstandard" usage appears. Leaving the mount point undefined
> forces anyone writing scripts or tools to consider whether they want to be
> portable and, if so, the proper way to find the cgroup hierarchies they need
> to manipulate.
Scanning /proc/mounts to find the relevant mount locations is pretty
simple, for code that's just wanting to use existing cgroup mounts.
But for the code that sets up mounts in the first place, its probably
helpful to have recommendations of suitable locations.
Paul
--
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