Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix thread pinning #134

Closed
khuck opened this issue Feb 27, 2021 · 1 comment
Closed

fix thread pinning #134

khuck opened this issue Feb 27, 2021 · 1 comment
Labels
bug enhancement

Comments

@khuck
Copy link
Collaborator

khuck commented Feb 27, 2021

On systems like summit, the set of available CPUs for a process is less than the total concurrency on the node. Replace the pthread_setaffinity_np() calls with sched_getaffinity() to get the range of cores, and then schedule_setaffinity() to choose the highest ranked hardware thread/core.
khuck added a commit that referenced this issue Mar 11, 2021
@khuck
Fixing bug #134.
10ca3bf 
Changing from pthread_setaffinity_np() to sched_get/setaffinity()
@khuck
Copy link
Collaborator Author

khuck commented Mar 11, 2021

Fixed with 10ca3bf

@khuck khuck closed this as completed Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@khuck