From: Jan Safranek <jsafrane@redhat.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
balbir@linux.vnet.ibm.com,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
containers@lists.linux-foundation.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bharata B Rao <bharata.rao@in.ibm.com>,
libcg-devel <libcg-devel@lists.sourceforge.net>,
"menage@google.com" <menage@google.com>
Subject: Re: [RFC] Mount point suggestions for cgroup
Date: Wed, 04 Nov 2009 17:24:46 +0100 [thread overview]
Message-ID: <4AF1AACE.6060705@redhat.com> (raw)
In-Reply-To: <20091104161142.GA8825@us.ibm.com>
On 11/04/2009 05:11 PM, Serge E. Hallyn wrote:
> Quoting Dave Hansen (dave@linux.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,
LSB (and FHS) IMHO does not specify any place for such stuff:
/dev - for devices only, cgroups are not devices
/mnt - for admin temporary mounts and "should not affect the manner in
which any program is run"
/var - for "any unsorted variable data", cgroups are not "unsorted
variable data", it's interface to kernel
FHS does not specify either /sys and /selinux and it seems to me nobody
complains about them.
/sys/cgroup would be the best, if sysfs supported mkdir(). But it does
not :(. Our kernel guys told me it's relatively easy to create new empty
directory /sys/cgroup (or /sys/kernel/cgroup), but it must be compiled
into kernel or a module. Then I could mount some tmpfs to it, create
/sys/cgroup/cpu, /sys/cgroup/memory etc. and mount the control group
hierarchies there... but as you can see, it's really really ugly thing
to do.
Jan
next prev parent reply other threads:[~2009-11-04 16:25 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 6:30 [RFC] Mount point suggestions for cgroup Balbir Singh
2009-11-04 6:40 ` KAMEZAWA Hiroyuki
2009-11-04 8:16 ` Balbir Singh
2009-11-04 15:21 ` Dave Hansen
2009-11-04 16:02 ` Jan Safranek
2009-11-04 16:05 ` Balbir Singh
2009-11-04 16:09 ` Dhaval Giani
[not found] ` <20091104160910.GN5495-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2009-11-04 16:27 ` Mark Hounschell
2009-11-04 16:27 ` Mark Hounschell
[not found] ` <20091104160530.GI3560-SINUvgVNF2CyUtPGxGje5AC/G2K4zDHf@public.gmane.org>
2009-11-04 16:09 ` Dhaval Giani
2009-11-04 16:38 ` Gabor Gombas
2009-11-04 16:38 ` Gabor Gombas
[not found] ` <4AF1A58E.1020003-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-11-04 16:05 ` Balbir Singh
2009-11-04 16:02 ` Jan Safranek
2009-11-04 16:11 ` Serge E. Hallyn
2009-11-04 16:11 ` Serge E. Hallyn
2009-11-04 16:18 ` Balbir Singh
[not found] ` <20091104161142.GA8825-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-11-04 16:18 ` Balbir Singh
2009-11-04 16:20 ` Dave Hansen
2009-11-04 16:24 ` Jan Safranek
2009-11-04 16:35 ` Alan Cox
2009-11-04 16:20 ` Dave Hansen
2009-11-04 16:24 ` Jan Safranek [this message]
[not found] ` <4AF1AACE.6060705-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-11-05 8:26 ` Gabor Gombas
2009-11-05 8:26 ` Gabor Gombas
2009-11-04 16:35 ` Alan Cox
[not found] ` <20091104081618.GD3560-SINUvgVNF2CyUtPGxGje5AC/G2K4zDHf@public.gmane.org>
2009-11-04 15:21 ` Dave Hansen
2009-11-04 17:19 ` Paul Menage
[not found] ` <20091104154024.0b8f6123.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-11-04 8:16 ` Balbir Singh
2009-11-04 17:19 ` Paul Menage
2009-11-04 17:35 ` Matt Helsley
2009-11-04 17:35 ` Matt Helsley
2009-11-04 21:25 ` Paul Menage
[not found] ` <6599ad830911041325i9b309a7y4d912d6be7ddbdd9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-04 21:40 ` Dhaval Giani
2009-11-04 23:37 ` Matt Helsley
2009-11-04 21:40 ` Dhaval Giani
[not found] ` <20091104214030.GO5495-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2009-11-04 23:34 ` KOSAKI Motohiro
2009-11-04 23:34 ` KOSAKI Motohiro
2009-11-04 23:37 ` Matt Helsley
[not found] ` <20091104173517.GA3668-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2009-11-04 21:25 ` Paul Menage
2009-11-07 15:23 ` Linus Walleij
2009-11-07 15:23 ` Linus Walleij
[not found] ` <20091104063005.GC3560-SINUvgVNF2CyUtPGxGje5AC/G2K4zDHf@public.gmane.org>
2009-11-04 6:40 ` KAMEZAWA Hiroyuki
2009-11-04 16:44 ` Daniel Lezcano
2009-11-08 17:05 ` Pavel Machek
2009-11-04 16:44 ` Daniel Lezcano
2009-11-05 12:07 ` Jan Safranek
2009-11-06 7:32 ` Balbir Singh
[not found] ` <4AF2C000.3020807-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-11-06 7:32 ` Balbir Singh
[not found] ` <4AF1AF68.40704-GANU6spQydw@public.gmane.org>
2009-11-05 12:07 ` Jan Safranek
2009-11-08 17:05 ` Pavel Machek
2009-11-09 5:05 ` Balbir Singh
[not found] ` <20091108170512.GB1372-+ZI9xUNit7I@public.gmane.org>
2009-11-09 5:05 ` Balbir Singh
-- strict thread matches above, loose matches on Subject: below --
2009-11-04 6:30 Balbir Singh
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=4AF1AACE.6060705@redhat.com \
--to=jsafrane@redhat.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=bharata.rao@in.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=libcg-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=serue@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.