Hi,
Sean has left the following comment at Integrate new thread affinity
interface into LIBBU and LIBRT
http://www.google-melange.com/gci/task/view/google/gci2012/8070202:
But the parent thread is modifying it
Even if they're read-only, the parent thread modifies the value and uses
the cpu_id to set the affinity (among other things). If it's not a
per-thread instance, then there indeed is a problem since the scheduler
could pause a thread after creation (context switch, cpu load, lots of
threads, whatever) yet the main loop continues to increment cpu_id and
create more threads. It'd be technically possible for all threads to read
cpu_id as the max value, which would be bad (with affinity, it's reduce
computation to a single processor).
Greetings,
The Google Open Source Programs Team
---
You are receiving this message because you are subscribed to Integrate new
thread affinity interface into LIBBU and LIBRT.
To stop receiving these messages, go to:
http://www.google-melange.com/gci/task/view/google/gci2012/8070202.
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
BRL-CAD Tracker mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-tracker
