[MOAB-dev] thread safety

[Grindeanu, Iulian R.]

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