Le 25/09/2011 21:05, Gabriele Fatigati a écrit : > Ok, > > so, set_membind() merged with HWLOC_MEMBIND_BIND is useless?
It's likely the most useful memory binding case. It's similar to what numactl --membind does for instance, very common. > The behaviour I want to set is it possible? I just said "you have to touch right after malloc." Brice > > 2011/9/25 Brice Goglin <brice.gog...@inria.fr > <mailto:brice.gog...@inria.fr>> > > Le 25/09/2011 20:57, Gabriele Fatigati a écrit : > > after done this, memory is allocated not in a local node of thread > > that does set_membind and malloc, but in node of thread that > touches > > it. And I don't understand this behaviour :( > > Memory is allocated when first-touched. If there's no area-specific > policy, it's allocated according to the policy of the thread that > touches, not according to the policy of the one that did malloc. > If you > want to follow the malloc'er thread, you have to touch right after > malloc. > > Brice > > > _______________________________________________ > hwloc-users mailing list > hwloc-us...@open-mpi.org <mailto:hwloc-us...@open-mpi.org> > 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 <http://www.cineca.it> Tel: +39 051 > 6171722 > > g.fatigati [AT] cineca.it <http://cineca.it> > > > _______________________________________________ > hwloc-users mailing list > hwloc-us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users