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

Proper CPU pinning. #77

Closed
vext01 opened this issue Oct 28, 2015 · 5 comments
Closed

Proper CPU pinning. #77

vext01 opened this issue Oct 28, 2015 · 5 comments
Assignees
@vext01
Labels
enhancement medium priority (a clear improvement but not a blocker)
Milestone
camera-ready

Comments

@vext01
Copy link
Member

vext01 commented Oct 28, 2015

At current, isolcpus on Linux only blocks user processes from a CPU and not kernel threads.

There is a tool called cset which might allow us to do proper CPU isolation, kernel threads and all. For a while it has been broken on Linux. I reported a bug to debian a while ago and they have finally responded saying it should be fixed:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796893
@vext01 vext01 self-assigned this Oct 28, 2015
@ltratt
Copy link
Member

ltratt commented Oct 28, 2015

"We believe that the bug you reported is fixed in the latest version of cpuset, which is due to be installed in the Debian FTP archive." I wonder when? If it's put in during the next few days, we could make use of it. Otherwise, perhaps it's for run number 2...

@vext01 vext01 added this to the post-submission milestone Nov 5, 2015
@vext01
Copy link
Member Author

vext01 commented Nov 5, 2015

Going to suggest this as post-submission.

@ltratt
Copy link
Member

ltratt commented Nov 5, 2015

It's still surely better to do some pinning? At least excluding other user tasks is almost certainly better than not doing so at all.

@vext01
Copy link
Member Author

vext01 commented Nov 5, 2015

At current, isolcpus on Linux only blocks user processes from a CPU and not kernel threads.

We currently use isolcpus, so we do have some pinning at least.

@vext01
Copy link
Member Author

vext01 commented Jan 14, 2016

This is now irrelevant, as we found that pinning introduces artificial CPU contention between threads.

@vext01 vext01 closed this as completed Jan 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vext01 vext01

Labels
enhancement medium priority (a clear improvement but not a blocker)
Projects
None yet
Milestone
camera-ready
Development

No branches or pull requests
2 participants
@ltratt @vext01