On Fri, Sep 14, 2012 at 11:53:24AM -0700, Tejun Heo wrote: [..] > In addition, for some resources, granularity beyond certain point > simply doesn't work. Per-service granularity might make sense for cpu > but applying it by default would be silly for blkio. Hmm.., In that case how libvirt will make use of blkio in the proposed scheme. We can't disable blkio nesting at "system" level. So We will have to disable it at each service level except "libvirtd" so that libvirt can use blkio for its virtual machines. That means blkio will see each service in a cgroup of its own and if that does not make sense by default, its a problem. In the existing scheme, atleast every service does not show up in its cgroup from blkio point of view. Everthig is in root and libvirt can create its own cgroups, keeping number of cgroups small. Thanks Vivek -- 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
