mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Jan Safranek <jsafrane@redhat.com>
Cc: Daniel Lezcano <daniel.lezcano@free.fr>,
	libcg-devel <libcg-devel@lists.sourceforge.net>,
	"menage@google.com" <menage@google.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	containers@lists.linux-foundation.org,
	Bharata B Rao <bharata.rao@in.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Dhaval Giani <dhaval@linux.vnet.ibm.com>
Subject: Re: [RFC] Mount point suggestions for cgroup
Date: Fri, 6 Nov 2009 13:02:08 +0530	[thread overview]
Message-ID: <20091106073208.GA4992@balbir.in.ibm.com> (raw)
In-Reply-To: <4AF2C000.3020807@redhat.com>

* Jan Safranek <jsafrane@redhat.com> [2009-11-05 13:07:28]:

> On 11/04/2009 05:44 PM, Daniel Lezcano wrote:
> >Balbir Singh wrote:
> >>Hi, All,
> >>
> >>We've been having a discussion as to what would be the right place to
> >>mount the cgroup filesystem. Jan has been proactively looking into
> >>this. The FHS has no recommendation since cgroup filesystem came in
> >>much later.
> >>
> >>The options are
> >>
> >>1. /dev/cgroup
> >>2. /cgroup
> >>3. Some place under /sys
> >>
> >>The problem with (2) is that it is quite non-standard and pollutes the
> >>root directory. (3) requires some basic support to create a directory
> >>for cgroup under /sys. (1) seems the most obvious choice since cpusets
> >>were mounted under /dev/cpuset, but /dev is controlled by udev.
> >>
> >>Given the three choices or any other suggestions, is there a general
> >>preference as to where we can mount it? The goal is to standardize
> >>the mount point (if possible).
> >Why the mount point has to be standardized ?
> >
> 
> The mount point does not need to be set into stone so everybody
> *must* use it. I, as Fedora packager, just need some default place
> where to mount it, so applications which need to create/manage
> groups work without any (potentially dumb) user assistance. 

I see no consensus, there are different approaches people like. I
wonder if we can create an empty directory under /sys/kernel/cgroup,
if so we would have supported the /sys approach. I'll send out a patch
to do the same.


Of
> course, advanced admin can change the settings and move the groups
> anywhere, applications still need to parse /proc/mounts or use
> appropriate library like libcgroup.

Agreed.

-- 
	Balbir

  reply	other threads:[~2009-11-06  7:32 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
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 [this message]
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=20091106073208.GA4992@balbir.in.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=bharata.rao@in.ibm.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=daniel.lezcano@free.fr \
    --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 \
    --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®