On Mon, Jun 03, 2013 at 07:13:02PM -0700, Tejun Heo wrote: > Some resources controlled by cgroup aren't per-task and cgroup core > allowing threads of a single thread_group to be in different cgroups > forced memcg do explicitly find the group leader and use it. This is > gonna be nasty when transitioning to unified hierarchy and in general > we don't want and won't support granularity finer than processes. With libvirt and KVM we require the ability to put different threads in different cgroups for the "cpu", "cpuset" & "cpuacct" controllers. This is to allow us to control schedular tunables / placement for QEMU vCPU threads, independantly of limits for QEMU I/O threads. So requiring all threads of a process to be in the same cgroup isn't sufficiently flexible for our needs. We don't care about this for the other non-CPU related controllers though. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- 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
