On Tue, Jul 15, 2014 at 03:36:27PM +0200, Peter Zijlstra wrote: > So, just to expand on this, we're already getting 'bug' reports because > worker threads are not cgroup aware. If work gets generated inside some > cgroup, the worker doesn't care and runs the worker thread wherever > (typically the root cgroup). > > This means that the 'work' escapes the cgroup confines and creates > resource inversion etc. The same is of course true for nice and RT > priorities. > > TJ, are you aware of this and/or given it any throught? Yeap, I'm aware of the issue but haven't read any actual bug reports yet. Can you point me to the reports? Given that worker pool management is dynamic, spawning separate pools for individual cgroups on-demand should be doable. Haven't been able to decide how much we should be willing to pay in terms of complexity yet. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
