public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Thadeu Lima de Souza Cascardo <cascardo@minaslivre.org>
Cc: debian-devel@lists.debian.org, linux-kernel@vger.kernel.org,
	containers@lists.linux-foundation.org
Subject: Re: cgroup mount point
Date: Mon, 02 Feb 2009 16:54:58 -0600	[thread overview]
Message-ID: <498779C2.2060908@nortel.com> (raw)
In-Reply-To: <20090202214153.GV3643@vespa.holoscopio.com>

Thadeu Lima de Souza Cascardo wrote:

> Linux Documentation is not consistent and have some funny options. In
> Documentation/cgroups/*, we have:

> 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.

I'd vote for "cgroups" or "containers", mounted at / or /sys/.

/opt feels more like where software should live, and /dev should be for 
devices rather than capabilities/management.  "cpuctl" and "cpuset" are 
subsets of the full capabilities of cgroups, so they're suboptimal as 
far as naming.

Chris

  reply	other threads:[~2009-02-02 22:55 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     ` cgroup mount point Thadeu Lima de Souza Cascardo
2009-02-02 22:54       ` Chris Friesen [this message]
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=498779C2.2060908@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=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