Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [hwloc-devel] thread safety
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2010-03-12 10:35:44


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?

-- 
Jeff Squyres
jsquyres_at_[hidden]
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/