Open MPI logo

Hardware Locality Users' 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-users] hwloc set membind function
From: Brice Goglin (Brice.Goglin_at_[hidden])
Date: 2011-09-25 14:35:28

Le 25/09/2011 20:27, Gabriele Fatigati a écrit :
> 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.

Why do you call set_membind() here? It's whole point is to change the
allocation policy of the current thread. If this thread then
first-touches some data, this data will obviously get allocated
acocording to set_membind().

If you don't want set_membind() to modify the allocation policy of the
current thread, why do you call it?