On Fri, Jun 07, 2013 at 12:21:19PM +0200, Kay Sievers wrote: > On Fri, Jun 7, 2013 at 12:12 PM, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote: > > > Well we pretty much needs the tunables available in the cpu, cpuset > > and cpuacct controllers to be available for the set of non-vCPU threads > > as a group. eg, cpu_shares, cfs_period_us, cfs_quota_us, cpuacct.usage, > > cpuacct.usage_percpu, cpuset.cpus, cpuset.mems. > > The cpu, cpuset, cpuacct controllers need different configuration per > controller, or do you refer them as one entity? They can all be co-mounted/merged without trouble, as they're treated all the same way. 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 :| _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers