On 06/07/2013 02:12 PM, Daniel P. Berrange wrote: >> The problem is that it doesn't make any sense to split threads of the >> same process for at least two major controllers and you end up with >> situation where you can't identify a resource to be belonging to a >> certain cgroup because such level of granularity is simply undefined. >> As I wrote before, we can special case certain controllers but I'm >> extremely reluctant. If you need it, please convince me. It seems quite valid for me to split priority threads in a process and give them a 80 % timeslice guarantee, while leaving only 20 % for low-prio threads (for instance). In general, I don't think that it would hurt to allow separation at thread level *for the leaves*, specifically at the cpu related controllers. -- 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
