4 ms·
I re-did the experiment again with `taskset` and got the same results, i.e. the mask is independent of creation of the "Guaranteed QoS" Pod. FWIW, `taskset` us
by n3t 3y ago
I re-did the experiment again with `taskset` and got the same results, i.e. the mask is independent of creation of the "Guaranteed QoS" Pod.
FWIW, `taskset` uses the same syscall as `nproc` (according to `strace`).
- jeffbee 3y agoPerhaps it is an artifact of your and my various container runtimes. For me, in a guaranteed qos pod, taskset shows just 1 visible CPU for a Guaranteed QoS pod with limit=request=1. # taskset -c -p 1 pid 1's current affinity list: 1 # nproc 1 I honestly do not see how it can work otherwise.
- n3t 3y agoAfter reading https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/#cpu-management-policies https://kubernetes.io/docs/tasks/administer-cluster/cpu-mana..., I think we have different policies set for the CPU Manager. In my case it's `"cpuManagerPolicy": "none"` and I suppose you're using `"static"` policy. Well, TIL. Thanks!
- jeffbee 3y agoTIL also. The difference between guaranteed and burstable seems meaningless without this setting.