On Fri, Sep 14, 2012 at 9:29 PM, Tejun Heo <tj@xxxxxxxxxx> wrote: > On Fri, Sep 14, 2012 at 09:58:30AM -0400, Vivek Goyal wrote: >> I am little concerned about above and wondering how systemd and libvirt >> will interact and behave out of the box. >> >> Currently systemd does not create its own hierarchy under blkio and >> libvirt does. So putting all together means there is no way to avoid >> the overhead of systemd created hierarchy. >> >> \ >> | >> +- system >> | >> +- libvirtd.service >> | >> +- virt-machine1 >> +- virt-machine2 >> >> So there is now way to avoid the overhead of two levels of hierarchy >> created by systemd. I really wish that systemd gets rid of "system" >> cgroup and puts services directly in top level group. Creating deeper >> hieararchices is expensive. The idea here is to split equally between the "system" and the "user"s at that level. That all can be re-considered and changed if really needed, but it's not an unintentionally created directory. Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
