[MOAB-dev] thread safety

Lorenzo Alessio Botti bottilorenzo at gmail.com
Fri Oct 3 13:59:37 CDT 2014


Vijay, thanks for the infos about your future plans. 
I’m very pleased to know that you also have the same needs.

I’ll try to use *_iterate calls, even if I’m not sure I completely understand how those works.
Is there a moab test case showing their usage?

Thanks again.
Lorenzo

On 03 Oct 2014, at 18:19, Vijay S. Mahadevan <vijay.m at gmail.com> wrote:

> Lorenzo, we are starting to invest time into making MOAB completely
> thread-safe. As Iulian mentioned, if you have immediate needs, the
> best method would be to stick with the *_iterate calls that basically
> just query the contiguous arrays in memory. If you see any
> inconsistent behaviors, please do send us a small test case so that we
> can replicate it.
> 
> We are planning to verify the API functions in Core/Interface and
> ParallelComm as a first step in preparation for the next minor
> release, some time around Dec, 2014. If you have contributions, those
> would be much appreciated too. Also, if there are other API functions
> that pose a priority, let us know.
> 
> Vijay
> 
> On Fri, Oct 3, 2014 at 9:46 AM, Grindeanu, Iulian R. <iulian at mcs.anl.gov> wrote:
>> How are you planing to use these?
>> can you share some code?
>> 
>> I think we are using some hints for the next similar calls, which may not be thread safe.
>> One solution would be to use direct access to memory calls, which return pointers in memory, for contiguous access.
>> 
>> so we could use tag_iterate, coords_iterate, connect_iterate.
>> The disadvantage is that an extra loop is needed if the sequences are broken.
>> 
>> Iulian
>> 
>> ________________________________________
>> From: moab-dev-bounces at mcs.anl.gov [moab-dev-bounces at mcs.anl.gov] on behalf of Paul Wilson [wilsonp at engr.wisc.edu]
>> Sent: Friday, October 03, 2014 8:38 AM
>> To: Lorenzo Alessio Botti; MOAB-dev at mcs.anl.gov
>> Subject: Re: [MOAB-dev] thread safety
>> 
>> Hi Lorenzo,
>> 
>> We also have quite urgent needs for this and have begun looking at it
>> for our use cases.
>> 
>> Paul
>> 
>> On 10/03/2014 04:44 AM, Lorenzo Alessio Botti wrote:
>>> Dear all,
>>> trying to playing around with some threaded code I seem to understand that some moab interface methods are not thread safe.
>>> 
>>> I'm concurrently using, for example
>>> tag_get_data
>>> get_connectivity
>>> get_coords
>>> 
>>> Is my assertion correct or am I messing things up on my side?
>>> If so, do you have any plans to implement a set, or a subset, of thread safe methods?
>>> 
>>> Thanks for the infos.
>>> Lorenzo
>> 
>> --
>> -- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ --
>> Paul Wilson ~ UW-Madison ~ 608-263-0807 ~ cal: http://bit.ly/pphw-cal
>> Professor, Engineering Physics. ~ http://cnerg.engr.wisc.edu
>> Faculty Director, Advanced Computing Infrastructure
>> 
>> 



More information about the moab-dev mailing list