Hi,
Skriptkid 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:
Maybe not
Each thread retaining it's own copy of the struct might not be needed. This
is pass by reference, agreed, but since it isn't being modified by
parallel_interface or parallel_interface_arg, the only places where it is
being accessed, I don't think that will be necessary. The struct is
required only to tell the thread which function has to be called, what the
arg is and what the thread ID is, so N structs would be a waste of
resources. Think of the struct as being only read and not written to by the
threads. Only data we set is read and no modification is done.
If there's any flaw in this theory of mine or if you'd still prefer each
thread having it's own copy, please tell me, and I'll do it :)
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
