-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VMA_INTERNAL_THREAD_AFFINITY doesn't run the vma internal thread on the specified core #1080
Comments
Could you please provide top of output using |
Hi Igor, thanks for your response. You can find the details below. If you need anything else, I can provide you with other information.
Running
Running
|
@pasis do you have explanation? |
Hi, @igor-ivanov @pasis is there any update on this issue? Thanks for your help. |
Is there any other way to find a solution or get support from libvma or Mellanox team? |
Subject
running with:
LD_PRELOAD=libvma.so VMA_SPEC=latency VMA_INTERNAL_THREAD_AFFINITY=2 ./app
However, VMA internal thread run on the same core with the application. I tried to use bit-mask approach to set the affinity it also didn't work.
Issue type
Configuration:
Actual behavior:
VMA_INTERNAL_THREAD_AFFINITY=2
doesn't have an impact on the core affinity of the vma process. It's running on the same core with the application thread. Causing context switches and hanging which impact the latency.Expected behavior:
The recommended configuration is to run VMA internal thread on a different core than the application but on the same NUMA node. To achieve this VMA_INTERNAL_THREAD_AFFINITY should work as expected to pin the vma process to the core we want it to be.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: