mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Helsley <matthltc@us.ibm.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Matt Helsley <matthltc@us.ibm.com>,
	Ben Blum <bblum@andrew.cmu.edu>,
	containers@lists.linux-foundation.org, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org,
	Lennart Poettering <lennart@poettering.net>,
	Paul Menage <menage@google.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] cgroupfs: create /sys/fs/cgroup to mount cgroupfs on
Date: Fri, 23 Jul 2010 13:21:48 -0700	[thread overview]
Message-ID: <20100723202148.GA5216@count0.beaverton.ibm.com> (raw)
In-Reply-To: <AANLkTikluqTBi3XsU-OT_IJuBdkURkHpM3ut-8ratnzr@mail.gmail.com>

On Fri, Jul 23, 2010 at 01:10:43AM +0200, Kay Sievers wrote:
> On Thu, Jul 22, 2010 at 23:48, Matt Helsley <matthltc@us.ibm.com> wrote:
> > So I'd suggest
> > those cgroup mounts go in /var/run/systemd/cgroup or something like that.
> 
> Impossible, we need it at bootup, and / is usually read-only, and /var
> might even be behind the network we need to bring up.
> 
> It needs to be on tmpfs mounted on the rootsfs, or in any of the
> virtual fss we have to mount anyway, so /sys/fs seems a good place.

Ahh, excellent point. Indeed, /sys/fs seems fine then.

Cheers,
	-Matt Helsley


  reply	other threads:[~2010-07-23 20:22 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 18:26 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 [this message]
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=20100723202148.GA5216@count0.beaverton.ibm.com \
    --to=matthltc@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bblum@andrew.cmu.edu \
    --cc=containers@lists.linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=lennart@poettering.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

Powered by JetHome