On Thu, Apr 06, 2017 at 12:42:04PM +0200, Michal Hocko wrote: > Is this something dictated by usecases which rely on isolcpus or rather > nobody bothered to implement one scheduling domain?
Its from the original use-case I suspect. It was done very much on purpose. If you want bigger partitions use cpusets. Or rather, like I've been saying for many years, use cpusets for everything and kill isolcpus. Problem with that last part is cgroups.. you then need to make a !root cgroup the 'default' cgroup in order to represent that. I really should've done this before all that cgroup crap came along, too late now :/
