[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091104161142.GA8825@us.ibm.com>
Date: Wed, 4 Nov 2009 10:11:42 -0600
From: "Serge E. Hallyn" <serue@...ibm.com>
To: Dave Hansen <dave@...ux.vnet.ibm.com>
Cc: 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>,
Bharata B Rao <bharata.rao@...ibm.com>,
libcg-devel <libcg-devel@...ts.sourceforge.net>,
"menage@...gle.com" <menage@...gle.com>,
Jan Safranek <jsafrane@...hat.com>
Subject: Re: [RFC] Mount point suggestions for cgroup
Quoting Dave Hansen (dave@...ux.vnet.ibm.com):
> On Wed, 2009-11-04 at 13:46 +0530, Balbir Singh wrote:
> > The reason I liked /dev/cgroup was because cpusets could be
> > mounted at /dev/cpuset or /dev/cgroup/cpuset. My concern with /cgroup
> > is that a ls "/" now becomes larger in size. But I'll take your vote
> > for it as +1 for /cgroup.
>
> /dev/pts is a decent precedent for doing it under /dev, although it does
> deal with actual devices. cgroups do not.
Hmm, on whose behalf are you making this decision?
LSB people will want to avoid using /cgroup, but I think a lot of
admins will likely prefer /cgroup (as I do). On my systems I
always use /cgroup, but would be more likely to use /mnt/cgroup
over /dev/cgroup.
lxc (at lxc.sf.net) rightfully takes the cgroupfs from wherever it
happens to be mounted. Do you really need a mountpoint decided?
If you do, then while I DETEST the extra typing, I think
/sys/kernel/cgroup makes most sense, since that's where you find
debugfs and securityfs.
-serge
--
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