Linux Container Development
 help / color / mirror / Atom feed
From: Lennart Poettering <mzerqung@0pointer.de>
To: Vivek Goyal <vgoyal@redhat.com>
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 23:11:36 +0200	[thread overview]
Message-ID: <20110720211135.GB14218@tango.0pointer.de> (raw)
In-Reply-To: <20110720205959.GG10079@redhat.com>

On Wed, 20.07.11 16:59, Vivek Goyal (vgoyal@redhat.com) wrote:

> 
> On Wed, Jul 20, 2011 at 10:28:32PM +0200, Lennart Poettering wrote:
> 
> [..]
> > systemd is and will always have to maintain its own hierarchy
> > independently of everybody else.
> 
> In the presentation today, you mentioned that you would like to create
> cgroups for users by default in cpu hierarchy (once RT time allocation
> issue is resolved). I am wondering what happens if an admin wants to
> change the policy a bit. Say give higher cpu shares to a specific
> user.

He can just go and do that. systemd assume to be the exclusive owner of
/sys/fs/cgroup/systemd, but the other hierarchies can be manipulated by
others too. That means that if people want to create a hierarchy there,
then they can do that. If people want systemd to stop mucking with the
cpu hierarchy for all users then this can be configured in a simple
config file.

> How is one supposed to do that. As it looks like that part of the
> control lies with systemd (as it is the one creates user group under
> cpu) and part of the control lies with GUItool/cgconfig.

Right now, systemd has few controls to actually make use of
controllers. It assumes that the limits on hte controllers are already
configured by something else.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

  reply	other threads:[~2011-07-20 21:11 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
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 [this message]
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=20110720211135.GB14218@tango.0pointer.de \
    --to=mzerqung@0pointer.de \
    --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=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