mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: Matt Helsley <matthltc@us.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	balbir@linux.vnet.ibm.com, containers@lists.linux-foundation.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jan@smtp1.linux-foundation.org,
	Bharata B Rao <bharata.rao@in.ibm.com>,
	libcg-devel <libcg-devel@lists.sourceforge.net>,
	Safranek <jsafrane@redhat.com>
Subject: Re: [RFC] Mount point suggestions for cgroup
Date: Thu, 5 Nov 2009 03:10:30 +0530	[thread overview]
Message-ID: <20091104214030.GO5495@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830911041325i9b309a7y4d912d6be7ddbdd9@mail.gmail.com>

On Wed, Nov 04, 2009 at 01:25:46PM -0800, Paul Menage wrote:
> On Wed, Nov 4, 2009 at 9:35 AM, Matt Helsley <matthltc@us.ibm.com> wrote:
> >
> > If anything, "standardizing" the mount point(s) will likely provide a false
> > sense of uniformity and we'll get some bad userspace scripts/tools that
> > break when "nonstandard" usage appears. Leaving the mount point undefined
> > forces anyone writing scripts or tools to consider whether they want to be
> > portable and, if so, the proper way to find the cgroup hierarchies they need
> > to manipulate.
> 
> Scanning /proc/mounts to find the relevant mount locations is pretty
> simple, for code that's just wanting to use existing cgroup mounts.
> But for the code that sets up mounts in the first place, its probably
> helpful to have recommendations of suitable locations.
> 

libcgroup uses a configuration file specified by the user to do this.

thanks,
-- 
regards,
Dhaval

  reply	other threads:[~2009-11-04 21:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04  6:30 Balbir Singh
2009-11-04  6:40 ` KAMEZAWA Hiroyuki
2009-11-04  8:16   ` Balbir Singh
2009-11-04 15:21     ` Dave Hansen
2009-11-04 16:02       ` Jan Safranek
2009-11-04 16:05         ` Balbir Singh
2009-11-04 16:09           ` Dhaval Giani
2009-11-04 16:27             ` Mark Hounschell
2009-11-04 16:38           ` Gabor Gombas
2009-11-04 16:11       ` Serge E. Hallyn
2009-11-04 16:18         ` Balbir Singh
2009-11-04 16:20         ` Dave Hansen
2009-11-04 16:24         ` Jan Safranek
2009-11-05  8:26           ` Gabor Gombas
2009-11-04 16:35         ` Alan Cox
2009-11-04 17:19   ` Paul Menage
2009-11-04 17:35   ` Matt Helsley
2009-11-04 21:25     ` Paul Menage
2009-11-04 21:40       ` Dhaval Giani [this message]
2009-11-04 23:34         ` KOSAKI Motohiro
2009-11-04 23:37       ` Matt Helsley
2009-11-07 15:23   ` Linus Walleij
2009-11-04 16:44 ` Daniel Lezcano
2009-11-05 12:07   ` Jan Safranek
2009-11-06  7:32     ` Balbir Singh
2009-11-08 17:05 ` Pavel Machek
2009-11-09  5:05   ` Balbir Singh

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=20091104214030.GO5495@linux.vnet.ibm.com \
    --to=dhaval@linux.vnet.ibm.com \
    --cc=Jan@smtp1.linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=bharata.rao@in.ibm.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=jsafrane@redhat.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=libcg-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.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

all inboxes | Powered by JetHome®