public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Paul Menage <menage@google.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
	Lennart Poettering <lennart@poettering.net>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Ben Blum <bblum@andrew.cmu.edu>,
	containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroupfs: create /sys/fs/cgroup to mount cgroupfs on
Date: Thu, 22 Jul 2010 11:53:01 -0700	[thread overview]
Message-ID: <20100722185301.GA528@suse.de> (raw)
In-Reply-To: <AANLkTimbcuzH6_bBhYX0U6vqftYgRwE0ZTmcbaRNzXef@mail.gmail.com>

On Thu, Jul 22, 2010 at 11:44:50AM -0700, Paul Menage wrote:
> On Thu, Jul 22, 2010 at 11:36 AM, Greg KH <gregkh@suse.de> wrote:
> >
> > Really?  I see systems mounting it at /cgroups/ in the filesystem today.
> 
> Sure, it *can* be mounted as a single instance, but you then lose
> flexibility. E.g. at Google we want to have a different hierarchy for
> the CPU subsystem (with the tree grouped according to
> latency-sensitive versus batch, etc) and memory (grouped according to
> what jobs are sharing memory with each other).
> 
> > Where are you expecting it to be mounted at?
> 
> I have no particular expectation. (At Google we're actually using
> /dev/cgroup/* but that's just for historical reasons, from
> /dev/cpuset). Under /sys/fs/cgroup sounds reasonable, but you'd want
> people to have the ability to manually create subdirs in there for
> separate mount points.

Ok, that's great, but it's not where the distros are starting to mount
it at.  As I learned with debugfs, you need to pick a location for
people to mount it at, otherwise it ends up all over the place.

If you are using /dev/cgroup/ that's nice, but I don't think that people
are expecting a whole filesystem under a /dev/ subdirectory.

I didn't realize that cgroupfs had so many different options that would
enable it to handle multiple mounts in this way.

Hm, Lennart, Kay, any ideas as to where to put it in a "standard" way?

thanks,

greg k-h

  reply	other threads:[~2010-07-22 18:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 18:26 [PATCH] cgroupfs: create /sys/fs/cgroup to mount cgroupfs on Greg KH
2010-07-22 18:31 ` Paul Menage
2010-07-22 18:36   ` Greg KH
2010-07-22 18:44     ` Paul Menage
2010-07-22 18:53       ` Greg KH [this message]
2010-07-22 19:07         ` Paul Menage
2010-07-22 19:12           ` Greg KH
2010-07-22 19:18             ` Paul Menage
2010-07-22 21:19               ` Greg KH
2010-07-22 23:12                 ` Paul Menage
2010-07-22 23:20                   ` Greg KH
2010-07-22 21:48             ` Matt Helsley
2010-07-22 23:10               ` Kay Sievers
2010-07-23 20:21                 ` Matt Helsley
2010-07-22 19:37     ` Vivek Goyal
2010-07-22 21:18       ` Greg KH
2010-07-22 21:26         ` Vivek Goyal
2010-07-22 23:35           ` Greg KH
2010-07-24 14:15           ` Balbir Singh
2010-07-22 23:08         ` Kay Sievers
2010-07-22 23:14           ` Greg KH
2010-07-22 23:16             ` Paul Menage
2010-07-22 23:23             ` Kay Sievers
2010-07-23  2:07             ` Vivek Goyal
2010-07-23 10:32               ` Jan Safranek
2010-07-23 12:06                 ` Greg KH
2010-07-26  9:08     ` Dhaval Giani
2010-07-26  9:12       ` Kay Sievers
2010-07-26  9:13         ` Dhaval Giani
2010-07-26 21:28           ` Greg KH
2010-07-26 21:55             ` Paul Menage
2010-07-26 22:05               ` Greg KH
2010-07-26 22:08                 ` Dhaval Giani
2010-07-26 22:17                   ` Greg KH
2010-07-26 22:09                 ` Paul Menage
2010-07-26 22:17                   ` Greg KH

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=20100722185301.GA528@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=bblum@andrew.cmu.edu \
    --cc=containers@lists.linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kay.sievers@vrfy.org \
    --cc=lennart@poettering.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --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