From: Thadeu Lima de Souza Cascardo <cascardo@minaslivre.org>
To: debian-devel@lists.debian.org
Cc: linux-kernel@vger.kernel.org, containers@lists.linux-foundation.org
Subject: Re: cgroup mount point
Date: Mon, 2 Feb 2009 19:41:53 -0200 [thread overview]
Message-ID: <20090202214153.GV3643@vespa.holoscopio.com> (raw)
In-Reply-To: <20090202205246.GA28593@glandium.org>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
On Mon, Feb 02, 2009 at 09:52:46PM +0100, Mike Hommey wrote:
> On Mon, Feb 02, 2009 at 09:26:11PM +0100, Julien Cristau wrote:
> > On Mon, 2009-02-02 at 18:00 -0200, Thadeu Lima de Souza Cascardo wrote:
> > > Hello,
> > >
> > > Some software I intend to package work with the new cgroup feature in
> > > Linux. I would like to open a discussion about what would be the better
> > > place to mount it and how/when to mount it.
> >
> > What do other distros use?
>
> Even better: what do the kernel folks want to do?
>
> Mike
From what I've seen, most of them are in the same phases as Debian, or,
perhaps, behind. Fedora seems to plan that for Fedora 11, and they have
some support in libvirt.
Linux Documentation is not consistent and have some funny options. In
Documentation/cgroups/*, we have:
cgroups.txt:
/dev/cgroup
cpuacct.txt:
/cgroups
devices.txt:
/cgroups
memcg_test.txt:
/opt/cgroup
/opt/cpuset
/cgroup
memory.txt:
/cgroups
cpusets.txt:
/dev/cpuset
freezer-subsystem.txt:
/containers
There is also:
Documentation/scheduler/sched-design-CFS.txt:
/dev/cpuctl
/cgroup
Documentation/scheduler/sched-rt-group.txt:
/cgroup
Documentation/accounting/cgroupstats.txt:
/cgroup
So, we have some more options now: /cgroups, /containers, /dev/cpuset,
/dev/cpuctl, /opt/cgroup, /opt/cpuset.
I am copying the container and the kernel guys. Perhaps, we can find an
agreement (if we want to find one at all) and change all that
Documentation to get consistent.
Regards,
Cascardo.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next parent reply other threads:[~2009-02-02 21:42 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 [this message]
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
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=20090202214153.GV3643@vespa.holoscopio.com \
--to=cascardo@minaslivre.org \
--cc=containers@lists.linux-foundation.org \
--cc=debian-devel@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
/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®