From: Greg KH <gregkh@suse.de>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Vivek Goyal <vgoyal@redhat.com>, Paul Menage <menage@google.com>,
Li Zefan <lizf@cn.fujitsu.com>,
Lennart Poettering <lennart@poettering.net>,
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,
"Daniel P. Berrange" <berrange@redhat.com>,
Jan Safranek <jsafrane@redhat.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH] cgroupfs: create /sys/fs/cgroup to mount cgroupfs on
Date: Thu, 22 Jul 2010 16:14:01 -0700 [thread overview]
Message-ID: <20100722231401.GA11538@suse.de> (raw)
In-Reply-To: <AANLkTinFQtwrCC82T9KlKskDV8fn-zYgimyH2wguHkqY@mail.gmail.com>
On Fri, Jul 23, 2010 at 01:08:12AM +0200, Kay Sievers wrote:
> On Thu, Jul 22, 2010 at 23:18, Greg KH <gregkh@suse.de> wrote:
> >> For my testing I now always use /cgroup/ and create directories under it
> >> /cgroup/blkio /cgroup/cpu etc and mount controllers on respective
> >> directories.
> >
> > Lennart and Kay, is this what systemd is doing? I really don't think we
> > should be adding a root /cgroup/ mount point to the system for something
> > like this.
>
> Already solved. Systemd always mounts an empty tmpfs at the 'cgroup'
> mountpoint, and stuff is free to create subdirs there. Systemd itself
> mount 'systemd' there.
Ah, that makes it easier. Paul and Vivek, any objection to this patch
going in now?
thanks,
greg k-h
next prev parent reply other threads:[~2010-07-22 23:14 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
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 [this message]
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=20100722231401.GA11538@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=bblum@andrew.cmu.edu \
--cc=berrange@redhat.com \
--cc=containers@lists.linux-foundation.org \
--cc=jsafrane@redhat.com \
--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 \
--cc=vgoyal@redhat.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