You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need option for exclude some physical cpu cores from scheduling and cpu pinning.
Main reason is minimize side effects to other apps which can use cpu pinning too (dp-service).
We can inspire by virtlet.
Feature has to be compatible with overcommit vcpu: #167
and numa pining: #48
It will have higher priority in logic as overcommit vcpu. It means: we have to decrease blocked cpu first from count of total physical cores and after we can apply overcommit vcpu logic.
Blocked cpus cannot be used for pinning.
This feature has to be optional and it can be configurable with argument.
Basic example
Don't use 0 and 1 cores for VMs
--resource-manager-blocked-cpus=0,1
Motivation
Minimize side effects to other apps. Improve performance.
Summary
We need option for exclude some physical cpu cores from scheduling and cpu pinning.
Main reason is minimize side effects to other apps which can use cpu pinning too (dp-service).
We can inspire by virtlet.
Feature has to be compatible with overcommit vcpu: #167
and numa pining: #48
It will have higher priority in logic as overcommit vcpu. It means: we have to decrease blocked cpu first from count of total physical cores and after we can apply overcommit vcpu logic.
Blocked cpus cannot be used for pinning.
This feature has to be optional and it can be configurable with argument.
Basic example
Don't use 0 and 1 cores for VMs
--resource-manager-blocked-cpus=0,1
Motivation
Minimize side effects to other apps. Improve performance.
Related issues
The text was updated successfully, but these errors were encountered: