We should probably improve that warning. It most likely means that libnuma isn't available on that node, but basically it is reporting that hwloc is unable to set the memory binding policy to ensure that all memory is local to the cpu-bound location.
On Mar 14, 2012, at 8:06 AM, Rolf vandeVaart wrote: > I am running a simple test and using the -bind-to-core or -bind-to-socket > options. I think the CPU binding is working fine, but I see these warnings > about not being able to bind to memory. Is this expected? This is trunk > code (266128) > > [dt]$ mpirun --report-bindings -np 2 -bind-to-core connectivity_c > -------------------------------------------------------------------------- > WARNING: a request was made to bind a process. While the system supports > binding the process itself, at least one node does NOT support binding memory > to the process location. > > Node: dt > > This is a warning only; your job will continue, though performance may be > degraded. > -------------------------------------------------------------------------- > [dt:03600] [[52612,0],0] odls:default binding child [[52612,1],1] to cpus 1,5 > [dt:03600] [[52612,0],0] odls:default binding child [[52612,1],0] to cpus 0,4 > [dt:03601] [[52612,1],0] is bound to cpus 0,4 > [dt:03602] [[52612,1],1] is bound to cpus 1,5 > Connectivity test on 2 processes PASSED. > > I see this on two different clusters. > > ----------------------------------------------------------------------------------- > This email message is for the sole use of the intended recipient(s) and may > contain > confidential information. Any unauthorized review, use, disclosure or > distribution > is prohibited. If you are not the intended recipient, please contact the > sender by > reply email and destroy all copies of the original message. > ----------------------------------------------------------------------------------- > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
