From: Mike Hommey <mh@glandium.org>
To: Paul Menage <menage@google.com>
Cc: Gustavo Noronha <kov@debian.org>,
debian-devel@lists.debian.org, linux-kernel@vger.kernel.org
Subject: Re: cgroup mount point
Date: Tue, 3 Feb 2009 19:49:15 +0100 [thread overview]
Message-ID: <20090203184915.GA10004@glandium.org> (raw)
In-Reply-To: <6599ad830902030855h1753f4a4o3a303b4dbddf10de@mail.gmail.com>
On Tue, Feb 03, 2009 at 08:55:34AM -0800, Paul Menage wrote:
> On Tue, Feb 3, 2009 at 6:38 AM, Gustavo Noronha <kov@debian.org> wrote:
> > On Tue, 2009-02-03 at 23:44 +1100, Ben Finney wrote:
> >> I agree with all that Thadeu Lima says here. I would add that cgroups
> >> are nothing to do with device nodes, so definitely don't belong in
> >> '/dev/' either.
> >>
> >> Since they're a filesystem mapping "for browsing and manipulation
> >> from user space" of a kernel facility, I think '/sys/cgroups/' is
> >> appropriate.
> >
> > I agree with this point of view. I believe /sys/cgroups is the way to
> > go. Now, of course this has the drawback of shadowing something future
> > versions of Linux would make available at that same path, but I am
> > pretty sure they would be careful not to do that after distributions
> > have settled on a standard path.
>
> Having one virtual filesystem mounted on top of another virtual
> filesystem seems like a recipe for problems.
Like with /sys/fs/fuse/connections ? Come on, there is no problem with a
virtual filesystem mounted on top of another.
Mike
next prev parent reply other threads:[~2009-02-03 19:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090202200013.GU3643@vespa.holoscopio.com>
[not found] ` <1233606371.15779.32.camel@radis.liafa.jussieu.fr>
[not found] ` <20090202205246.GA28593@glandium.org>
2009-02-02 21:41 ` Thadeu Lima de Souza Cascardo
2009-02-02 22:54 ` Chris Friesen
2009-02-02 23:43 ` Thadeu Lima de Souza Cascardo
2009-02-03 3:15 ` KAMEZAWA Hiroyuki
2009-02-03 5:06 ` Serge E. Hallyn
2009-02-06 6:17 ` Balbir Singh
2009-02-03 10:24 ` Daniel P. Berrange
2009-02-03 12:30 ` Thadeu Lima de Souza Cascardo
2009-02-03 13:26 ` Daniel P. Berrange
[not found] ` <87ljsnzo4v.fsf@benfinney.id.au>
2009-02-03 12:57 ` Thadeu Lima de Souza Cascardo
2009-02-04 3:59 ` Ben Finney
2009-02-03 14:38 ` Gustavo Noronha
2009-02-03 16:55 ` Paul Menage
2009-02-03 18:49 ` Mike Hommey [this message]
2009-02-03 18:51 ` sean finney
2009-02-03 19:14 ` Paul Menage
2009-02-03 23:38 ` Harald Braumann
2009-02-03 23:40 ` Paul Menage
2009-02-04 0:18 ` Harald Braumann
2009-02-04 9:16 ` Josselin Mouette
2009-02-05 21:19 ` José Luis Tallón
2009-02-06 22:00 ` Harald Braumann
2009-02-03 15:03 ` Gabor Gombas
2009-02-03 16:19 ` Bill Nottingham
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=20090203184915.GA10004@glandium.org \
--to=mh@glandium.org \
--cc=debian-devel@lists.debian.org \
--cc=kov@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®