On Mar 11, 2010, at 10:12 PM, Brice Goglin wrote:
> I guess we a thread-safety section in hwloc.doxy to document that all
> topology modifiers (most of hwloc_topology_* functions, not all of them)
> cannot run concurrently.
To support that, do we need to make internal variables and fields be volatile?
If we say that applications need to provide their own synchronization between readers and writers, atomic writes shouldn't be an issue, right?
For corporate legal information go to: