Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 2
    Threads can be bound to a specific CPU with taskset(1) sched_setaffinity(2) or the pthread functions with similar names. It's something you should do only in very specific circumstances (e.g. on a special-purpose device with particular responsiveness objectives) or for testing. Most of the time, the kernel will decide which CPU to run a thread on better than a human could. Commented Oct 4, 2010 at 21:12
  • Yes - I know. That was what I intend to write but I wrote only about cpulimit by accident. Fixed by adding "& co.". Commented Oct 4, 2010 at 21:23
  • Is the conclusion from this that there is no way to track how my software is running on the hardware? Commented Oct 5, 2010 at 16:51
  • To large extend - yes. The threads are not usually bound to cores and most of them will not be runned at any particular moment. Commented Oct 5, 2010 at 21:29