mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: Jan Safranek <jsafrane@redhat.com>,
	Dave Hansen <dave@linux.vnet.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.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, 4 Nov 2009 21:39:10 +0530	[thread overview]
Message-ID: <20091104160910.GN5495@linux.vnet.ibm.com> (raw)
In-Reply-To: <20091104160530.GI3560@balbir.in.ibm.com>

On Wed, Nov 04, 2009 at 09:35:30PM +0530, Balbir Singh wrote:
> * Jan Safranek <jsafrane@redhat.com> [2009-11-04 17:02:22]:
> 
> > On 11/04/2009 04:21 PM, Dave Hansen wrote:
> > >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.
> > 
> > There is also /dev/shm, but IMHO that's not reason to pollute /dev
> > with filesystems that are not devices.
> >
> 
> Yep, but hasn't the pollution already occured with /dev/cpuset today? 
> sysfs would require work for changes to /sys, so do we go with Kame's
> suggestion of /cgroup?
> 

I vote for /cgroup as well.

thanks,
-- 
regards,
Dhaval

  reply	other threads:[~2009-11-04 16:10 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 [this message]
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
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=20091104160910.GN5495@linux.vnet.ibm.com \
    --to=dhaval@linux.vnet.ibm.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=jsafrane@redhat.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=libcg-devel@lists.sourceforge.net \
    --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®