[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100722211958.GB1297@suse.de>
Date: Thu, 22 Jul 2010 14:19:58 -0700
From: Greg KH <gregkh@...e.de>
To: Paul Menage <menage@...gle.com>
Cc: Li Zefan <lizf@...fujitsu.com>,
Lennart Poettering <lennart@...ttering.net>,
Kay Sievers <kay.sievers@...y.org>,
Andrew Morton <akpm@...ux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Ben Blum <bblum@...rew.cmu.edu>,
containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cgroupfs: create /sys/fs/cgroup to mount cgroupfs on
On Thu, Jul 22, 2010 at 12:18:13PM -0700, Paul Menage wrote:
> On Thu, Jul 22, 2010 at 12:12 PM, Greg KH <gregkh@...e.de> wrote:
> > I don't know if we want to encourage that as a mount point, do you?
>
> No.
Heh.
> > 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?
> >
>
> We don't particularly care about the names of the individual
> sub-mounts, since it's all programatically controlled. We just specify
> which subsystems we want grouped together (and a catch-all remainder
> hierarchy) and the system picks the name of one of the subsystems in
> the hierarchy to act as a unique mountpoint name (since each subsystem
> can only be in one hierarchy). So e.g. /dev/cgroup/cpuset, or
> /dev/cgroup/io
Thanks for the info. But in the end, I really don't want to see a
/cgroup/ mountpoint added to people's systems if at all possible.
Any suggestions from your side?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists