From: Paul Menage <menage@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: balbir@linux.vnet.ibm.com,
libcg-devel <libcg-devel@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
containers@lists.linux-foundation.org,
Jan Safranek <jsafrane@redhat.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Bharata B Rao <bharata.rao@in.ibm.com>
Subject: Re: [RFC] Mount point suggestions for cgroup
Date: Wed, 4 Nov 2009 09:19:18 -0800 [thread overview]
Message-ID: <6599ad830911040919k644a67cds713be3a0ea74e5d1@mail.gmail.com> (raw)
In-Reply-To: <20091104154024.0b8f6123.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, Nov 3, 2009 at 10:40 PM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> Then, to say my own not-seriously-considered idea, I vote for
> - /cgroup/[HierarchyName]/
> rather than /dev/ or /sys or /opt. This sounds straightforward.
We're using /dev/cgroup (for single mounts) or
/dev/cgroup/$hierarchy_name (for multiple-mount configurations) but
that's mostly just due to the historical accident of /dev/cpuset. So
/cgroup/$hierarchy_name sounds plausible, or /kernel/cgroup/... as
suggested in another email.
Paul
next prev parent reply other threads:[~2009-11-04 17:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 6:30 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
2009-11-04 16:27 ` Mark Hounschell
2009-11-04 16:38 ` Gabor Gombas
2009-11-04 16:11 ` Serge E. Hallyn
2009-11-04 16:18 ` Balbir Singh
2009-11-04 16:20 ` Dave Hansen
2009-11-04 16:24 ` Jan Safranek
2009-11-05 8:26 ` Gabor Gombas
2009-11-04 16:35 ` Alan Cox
2009-11-04 17:19 ` Paul Menage [this message]
2009-11-04 17:35 ` Matt Helsley
2009-11-04 21:25 ` Paul Menage
2009-11-04 21:40 ` Dhaval Giani
2009-11-04 23:34 ` KOSAKI Motohiro
2009-11-04 23:37 ` Matt Helsley
2009-11-07 15:23 ` Linus Walleij
2009-11-04 16:44 ` Daniel Lezcano
2009-11-05 12:07 ` Jan Safranek
2009-11-06 7:32 ` Balbir Singh
2009-11-08 17:05 ` Pavel Machek
2009-11-09 5:05 ` 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=6599ad830911040919k644a67cds713be3a0ea74e5d1@mail.gmail.com \
--to=menage@google.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=bharata.rao@in.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=jsafrane@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=libcg-devel@lists.sourceforge.net \
--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®