Open MPI logo

Hardware Locality Users' Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Hardware Locality Users mailing list

Subject: Re: [hwloc-users] hwloc set membind function
From: Gabriele Fatigati (g.fatigati_at_[hidden])
Date: 2011-09-25 14:27:41


>set_membind done by thread 2 has no reference with malloc(array) done by
first thread, so why it influence the real >allocation of this array?

It doesn't.

In my example seems yes...

if(tid==0){

 set_membind(HWLOCMEMBIND_BIND, node 0)
 malloc(array)...

}

if (tid==1){
 set_membind(HWLOCMEMBIND_BIND, node 1)

for(i...)
  array(i)
}

end parallel region

array is allocated on node 1, not node 0 as I expected So it seems
set_membind() of second thread influence in some manner array allocation
using first touch.

2011/9/25 Brice Goglin <Brice.Goglin_at_[hidden]>

> **
> Le 25/09/2011 12:41, Gabriele Fatigati a écrit :
>
>
>> * doing two set_area_membind on the same entire array is useless, the
> second one will overwrite the first one.
>
> But set_area_membind is for memory in general, not for a particular
> malloc. ( Is it rigth?)
>
>
> It's for an memory area.
>
>
> set_membind done by thread 2 has no reference with malloc(array) done by
> first thread, so why it influence the real allocation of this array?
>
>
>
>
> Brice
>
>
> _______________________________________________
> hwloc-users mailing list
> hwloc-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users
>

-- 
Ing. Gabriele Fatigati
HPC specialist
SuperComputing Applications and Innovation Department
Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy
www.cineca.it                    Tel:   +39 051 6171722
g.fatigati [AT] cineca.it