Results 1 to 1 of 1
I'm having troubles with cpusets it will be great if you could help me. I've defined two cpuset groups: "cpuset_0" which has only one task, and "cpuset_1" which is for ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-17-2012 #1
- Join Date
- Oct 2012
scheduler & cpuset strange behavior
I'm having troubles with cpusets it will be great if you could help me.
I've defined two cpuset groups: "cpuset_0" which has only one task,
and "cpuset_1" which is for all the other tasks in my system.
"cpuset_0" has cpus="0", cpu_exclusive="1" and only the one task assign to it.
and "cpuset_1" has cpus="1-3", cpu_exclusive="0" and all the tasks I could move as root from the root cpuset (i.e. "/dev/cpuset/").
Both cpusets has mems="0".
The problem is that for some reason I see tasks which assigned to "cpuset_1" which are running on the exclusive cpu "cpuset_0"
For example running ps H -eo tid,psr,cgroup,cmd gives me:
2199 0 6:cpuset:/cpuset_1?5:freeze /usr/lib/chromium-browser/chromium-browser
among other processes which shouldn't be running on cpu 0.
I've tested it both on kernel 3.2.0 and 2.6.
And at the end I have to find a way of making it work on a production server running kernel 2.6.32.