From: Vivek Goyal <vgoyal@redhat.com>
To: Lennart Poettering <mzerqung@0pointer.de>
Cc: fedora-devel-list@redhat.com, containers@lists.osdl.org,
duffy@redhat.com, cg-manager-developers@lists.fedorahosted.org
Subject: Re: new cg-manager gui tool for managin cgroups
Date: Wed, 20 Jul 2011 16:42:40 -0400 [thread overview]
Message-ID: <20110720204240.GF10079@redhat.com> (raw)
In-Reply-To: <20110720202831.GA11395@tango.0pointer.de>
On Wed, Jul 20, 2011 at 10:28:32PM +0200, Lennart Poettering wrote:
[..]
>
> > Right now, the gui assumes that the various hierarchies are mounted separately,
> > but that the cpu and cpuacct are co-mounted. Its my understanding that this
> > is consistent with how systemd is doing things. So that's great.
>
> In F15 we mount all controllers enabled in the kernel separately. In F16
> we'll optionally mount some of them together, and we'll probably ship a
> default of mounting cpu and cpuacct together if they are both enabled.
Last time we talked about possibility of co-mounting memory and IO at some
point of time and you said it is a bad idea from applications programming
point of view. Has that changed now?
Thanks
Vivek
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
next prev parent reply other threads:[~2011-07-20 20:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 19:20 new cg-manager gui tool for managin cgroups Jason Baron
2011-07-20 20:28 ` Lennart Poettering
2011-07-20 20:42 ` Vivek Goyal [this message]
2011-07-20 21:07 ` Lennart Poettering
2011-07-20 21:26 ` Vivek Goyal
2011-07-20 21:41 ` Lennart Poettering
2011-07-20 20:59 ` Vivek Goyal
2011-07-20 21:11 ` Lennart Poettering
2011-07-21 14:20 ` Jason Baron
2011-07-21 15:08 ` Vivek Goyal
2011-07-21 16:11 ` Lennart Poettering
2011-07-21 23:08 ` Karel Zak
2011-07-22 0:32 ` Lennart Poettering
2011-07-22 10:13 ` Karel Zak
[not found] ` <20110721142053.GA2454-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-07-21 17:23 ` Tomas Mraz
[not found] ` <1311268987.6273.18.camel-ToA8MW0H8sPg+ylLNZCgDw@public.gmane.org>
2011-07-21 17:55 ` Lennart Poettering
2011-07-22 1:38 ` Ben Boeckel
2011-07-20 23:01 ` Matthias Clasen
2011-07-21 10:03 ` Daniel P. Berrange
2011-07-21 14:36 ` Jason Baron
[not found] ` <20110721143622.GB2454-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-07-21 14:52 ` Daniel P. Berrange
2011-07-21 15:28 ` Vivek Goyal
2011-07-21 15:36 ` Daniel P. Berrange
[not found] ` <20110721153620.GO17632-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-07-21 15:53 ` Lennart Poettering
2011-07-21 20:15 ` Jason Baron
2011-07-21 20:32 ` Vivek Goyal
2011-07-22 10:01 ` Daniel P. Berrange
[not found] ` <20110721152845.GD12373-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-07-21 16:36 ` Lennart Poettering
2011-08-02 14:04 ` Vivek Goyal
2011-07-21 16:17 ` Lennart Poettering
2011-07-21 20:58 ` Vivek Goyal
2011-07-22 10:07 ` Daniel P. Berrange
[not found] ` <20110720192029.GD2482-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-07-21 15:30 ` Daniel P. Berrange
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=20110720204240.GF10079@redhat.com \
--to=vgoyal@redhat.com \
--cc=cg-manager-developers@lists.fedorahosted.org \
--cc=containers@lists.osdl.org \
--cc=devel@lists.fedoraproject.org \
--cc=duffy@redhat.com \
--cc=fedora-devel-list@redhat.com \
--cc=mzerqung@0pointer.de \
/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