The good news is that it looks like even though Cpus_allowed says CPU 0 is allowed the scheduler isn't going to actually schedule anything in the cgroup to that CPU until something induces the cpuset code to rebuild the scheduler domains. Primarily that would be writing to one of the cpuset.cpus files, but it looks like one or two other events might cause it to happen, such as CPU hotplug. This bears out experimentally; tasks scheduled within the cgroup as in the above script only get scheduled on CPUs 1-3.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623143 Title: Linux container does not take same cpu configuration as kernet's hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
