Issue about using hyper-thread in exclusive mode about cpu-manager-for-kubernetes HOT 4 CLOSED

Hi, when using isolate with exclusive mode, CMK isolates on a core level. So, in your example, when the first task requests an exclusive core it takes both of the core's threads (2,38) and assigns them to the task, taking them both out of contention for other tasks to use.

Hope that clears things up.

from cpu-manager-for-kubernetes.

@phillyb7 I read the doc and example, you only talk about assign 1 core to 1 task. When I run cmk to assign multiple core to 1 task, just first core running the task. Can CMK make task run in multi core ?

from cpu-manager-for-kubernetes.

Hi @lamto20132223, this problem was also mentioned recently here #244

We're currently investigating the issue to see if it's an actual bug.

from cpu-manager-for-kubernetes.

Hi @phillyb7 I think this is problem about docker version or something.
When I assign 1 core to task it work perfect, but cannot assign 2 or more cores to 1 task
Look like taskset has some conflict with isolcpu like this link bellow
moby/moby#31086

from cpu-manager-for-kubernetes.