On Wed, 20.07.11 16:59, Vivek Goyal (vgoyal@xxxxxxxxxx) 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. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
