Hello all, Today I have a problem with the --map-to socket feature of Open MPI 2.1.1 when used with application context files.
In the examples below, I am testing on a 2 socket computer, each socket with 4 cores. --- Example 1: .../openmpi-2.1.1/bin/mpirun --report-bindings \ -map-by socket \ -np 2 \ afftest01.exe returns ...MCW rank 0 bound to socket 0 ... : [B/B/B/B][./././.] ...MCW rank 1 bound to socket 1 ... : [./././.][B/B/B/B] which is what I would expect. --- Example 2: Create appfile as: -np 1 afftest01.exe -np 1 afftest01.exe Then .../openmpi-2.1.1/bin/mpirun --report-bindings \ -map-by socket \ -app appfile returns ...MCW rank 0 bound to socket 0 ... : [B/B/B/B][./././.] ...MCW rank 1 bound to socket 0 ... : [B/B/B/B][./././.] which is not what I expect. I expect the same bindings as in Example 1. --- Example 3: Using the same appfile as in Example 2, .../openmpi-1.4.3/bin/mpirun --report-bindings \ -bysocket --bind-to-core \ -app appfile returns ... odls:default:fork binding child ... to socket 0 cpus 0002 ... odls:default:fork binding child ... to socket 1 cpus 0001 which is what I would expect. Here I use --bind-to-core just to get the bindings printed. --- The examples show that the --map-by socket feature does not work as expected when application context files are used. However the older -bysocket feature worked as expected in OpenMPI 1.4.3 when application context files are used. If I am using the wrong syntax in Example 2, please let me know. Sincerely, Ted Sussman
_______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users