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
{{ message }}
This repository has been archived by the owner on Jan 18, 2023. It is now read-only.
I create multiple processes by "cmk.py isolate --pool=shared ...". Then I use "cmk.py describe", and see them listed in the shared pool. However, their PSR are the same (see PSR by "ps -o psr "), though their core affinity are exactly the shared pool cores (see affinity by "taskset -pc "). I suppose their PSR should be spread over the shared pool cores, right?
I guess it is because the shared pool cores are isolate cores (i.e. the "isolcpus" in GRUB config), and OS does not schedule the processes over isolate cores. What else configurations should I do to make the processes' PSR spreading over the shared pool cores?
My environment
OS: Ubuntu 18.04.5
Kernel: 5.4.0-66-generic
CMK: 1.5.2
Thanks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I create multiple processes by "cmk.py isolate --pool=shared ...". Then I use "cmk.py describe", and see them listed in the shared pool. However, their PSR are the same (see PSR by "ps -o psr "), though their core affinity are exactly the shared pool cores (see affinity by "taskset -pc "). I suppose their PSR should be spread over the shared pool cores, right?
I guess it is because the shared pool cores are isolate cores (i.e. the "isolcpus" in GRUB config), and OS does not schedule the processes over isolate cores. What else configurations should I do to make the processes' PSR spreading over the shared pool cores?
My environment
OS: Ubuntu 18.04.5
Kernel: 5.4.0-66-generic
CMK: 1.5.2
Thanks!
The text was updated successfully, but these errors were encountered: