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 12:12:00 -0700 [thread overview]
Message-ID: <20100722191200.GA5609@suse.de> (raw)
In-Reply-To: <AANLkTik07hZot_x0p7xJuY8s4f8pGRd2Mn1+jYfHH2iq@mail.gmail.com>
On Thu, Jul 22, 2010 at 12:07:43PM -0700, Paul Menage wrote:
> On Thu, Jul 22, 2010 at 11:53 AM, Greg KH <gregkh@suse.de> wrote:
> >
> > 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.
>
> Sure - as I said that's just for historical reasons from when we
> migrated from cpusets which were traditionally mounted at /dev/cpuset,
> so it involved less change. There's no particular reason to mount it
> there (although having said that, what about /dev/pts and /dev/shm?).
Yeah, /dev/pts and /dev/shm are long-time users of the /dev filesystem.
I don't know if we want to encourage that as a mount point, do you?
What are the different names you are giving to your mount points now for
cgroupfs so I can get an idea of how it is used currently?
thanks,
greg k-h
next prev parent reply other threads:[~2010-07-22 19:12 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
2010-07-22 19:07 ` Paul Menage
2010-07-22 19:12 ` Greg KH [this message]
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=20100722191200.GA5609@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