[Lxc-users] [PATCH 2/2] cgroups: support cgroups mounted in multiple places

[Daniel Lezcano]

On 06/25/2011 08:19 PM, Michael H. Warfield wrote:
> On Sat, 2011-06-25 at 20:05 +0200, Daniel Lezcano wrote: 
>> On 06/24/2011 07:54 PM, Serge Hallyn wrote:
>>> I.e. with systemd or libcgroup.
>>>
>>> To do this, instead of looking for one cgroup called 'lxc' or
>>> otherwise taking the first cgroup we find, we actually create a
>>> container in every mounted cgroup fs.  Right now it's done under the
>>> root of each fs.  We may want to put that under lxc, or, better yet,
>>> make that configurable.
>>>
>>> Note the use of clone_children seems not quite right, but that's
>>> not for this patch to fix.  In particular, if clone_children is
>>> not in the mntopts, we reject it.  Yet later we try to set it
>>> ourselves.  I believe we should simply, if ns cgroup is not
>>> composed, always try to set clone_children to 1.  As it stands,
>>> with libcgroup installed, I had to do
>>>
>>>    cd /sys/fs/cgroup
>>>    for d in `/bin/ls`; do
>>>       echo 1 > $d/cgroup.clone_children
>>>    done
>>>
>>> But after that, 'lxc-start -n l1' worked like a charm.  It also
>>> continues to work with a single mount of cgroups under /cgroup.
>>>
>>> Signed-off-by: Serge Hallyn <serge.hallyn at ubuntu.com>
>>> ---
>> Ok, I installed f15 on a kvm machine. But WTF are all these daemons !!
>>
>> 1 root      20   0 48232  15m 1772 R 66.1  1.5   4:53.82
>> systemd              
>> 19247 dlezcano  20   0  790m  40m  11m R 62.2  4.0   0:46.93
>> gnome-settings-      
>> 19255 root      20   0  104m  27m 3252 R 35.9  2.8   0:44.83
>> packagekitd          
>> 1173 root      20   0  196m  65m 2416 R 30.6  6.5   2:43.70
>> udisks-daemon        
>>
>> ... eating all the cpu and making impossible to use the fedora ?
> Don't get me started, yeah...
>
> systemd and udisks-daemon should not be consuming that much cpu.  That
> is weird.
>
> Gnome-settings and packagekitd, I don't know.  Why do we need a bloody
> daemon to check for packages and updates?  I just don't know.
yep.

> OTOH...  I'm not experiencing that on Forest (my hard-iron F15 host
> engine).  My load average is staying low.  So I'm not sure what's going
> on for your.

Since I switched to multi-user.target (aka init 3), things are working
much better.