Re: [OMPI users] --map-by

> On Nov 21, 2017, at 8:53 AM, r...@open-mpi.org wrote: > >> On Nov 21, 2017, at 5:34 AM, Noam Bernstein > > wrote: >> >>> >>> On Nov 20, 2017, at 7:02 PM, r...@open-mpi.org >>> wrote: >>> >>> So

Re: [OMPI users] --map-by

I believe that map-by core with a PE > 1 may have worked at some point in the past, but the docs should probably be looked at. I took a (very brief) look at the code and re-enabling that particular option would be difficult and not really necessary since one can reproduce the desired pattern

Re: [OMPI users] --map-by

> On Nov 20, 2017, at 7:02 PM, r...@open-mpi.org wrote: > > So there are two options here that will work and hopefully provide you with > the desired pattern: > > * if you want the procs to go in different NUMA regions: > $ mpirun --map-by numa:PE=2 --report-bindings -n 2 /bin/true >

Re: [OMPI users] --map-by

So there are two options here that will work and hopefully provide you with the desired pattern: * if you want the procs to go in different NUMA regions: $ mpirun --map-by numa:PE=2 --report-bindings -n 2 /bin/true [rhc001:131460] MCW rank 0 bound to socket 0[core 0[hwt 0-1]], socket 0[core

Re: [OMPI users] --map-by

> On Nov 16, 2017, at 9:49 AM, r...@open-mpi.org wrote: > > Do not include the “bind-to core” option.the mapping directive already forces > that Same error message, unfortunately. And no, I’m not setting a global binding policy, as far as I can tell: env | grep OMPI_MCA

Re: [OMPI users] --map-by

Do not include the “bind-to core” option.the mapping directive already forces that Sent from my iPad > On Nov 16, 2017, at 7:44 AM, Noam Bernstein > wrote: > > Hi all - I’m trying to run mixed MPI/OpenMP, so I ideally want binding of > each MPI process to a

[OMPI users] --map-by

Hi all - I’m trying to run mixed MPI/OpenMP, so I ideally want binding of each MPI process to a small set of cores (to allow for the OpenMP threads). From the mpirun docs at https://www.open-mpi.org//doc/current/man1/mpirun.1.php I

Re: [OMPI users] "-map-by socket:PE=1" doesn't do what I expect

On Fri, 17 Feb 2017, r...@open-mpi.org wrote: Mark - this is now available in master. Will look at what might be required to bring it to 2.0 Thanks Ralph, To be honest, since you've given me an alternative, there's no rush from my point of view. The logic's embedded in a script and it's

Re: [OMPI users] "-map-by socket:PE=1" doesn't do what I expect

Mark - this is now available in master. Will look at what might be required to bring it to 2.0 > On Feb 15, 2017, at 5:49 AM, r...@open-mpi.org wrote: > > >> On Feb 15, 2017, at 5:45 AM, Mark Dixon wrote: >> >> On Wed, 15 Feb 2017, r...@open-mpi.org wrote: >> >>> Ah,

Re: [OMPI users] "-map-by socket:PE=1" doesn't do what I expect

> On Feb 15, 2017, at 5:45 AM, Mark Dixon wrote: > > On Wed, 15 Feb 2017, r...@open-mpi.org wrote: > >> Ah, yes - I know what the problem is. We weren’t expecting a PE value of 1 - >> the logic is looking expressly for values > 1 as we hadn’t anticipated this >>

Re: [OMPI users] "-map-by socket:PE=1" doesn't do what I expect

On Wed, 15 Feb 2017, r...@open-mpi.org wrote: Ah, yes - I know what the problem is. We weren’t expecting a PE value of 1 - the logic is looking expressly for values > 1 as we hadn’t anticipated this use-case. Is it a sensible use-case, or am I crazy? I can make that change. I’m off to a

Re: [OMPI users] "-map-by socket:PE=1" doesn't do what I expect

Ah, yes - I know what the problem is. We weren’t expecting a PE value of 1 - the logic is looking expressly for values > 1 as we hadn’t anticipated this use-case. I can make that change. I’m off to a workshop for the next day or so, but can probably do this on the plane. > On Feb 15, 2017,

Re: [OMPI users] "-map-by socket:PE=1" doesn't do what I expect

Ah, yes - I know what the problem is. We weren’t expecting a PE value of 1 - the logic is looking expressly for values > 1 as we hadn’t anticipated this use-case. I can make that change. I’m off to a workshop for the next day or so, but can probably do this on the plane. > On Feb 15, 2017,

[OMPI users] "-map-by socket:PE=1" doesn't do what I expect

Hi, When combining OpenMPI 2.0.2 with OpenMP, I'm interested in launching a number of ranks and allocating a number of cores to each rank. Using "-map-by socket:PE=", switching to "-map-by node:PE=" if I want to allocate more than a single socket to a rank, seems to do what I want. Except

Re: [OMPI users] map-by node with openmpi-1.7.5a1

I'm afraid that patch didn't solve the problem when I tested it - it resolved a problem of cpus-per-rank > 1, but not the case of descending order of slots. Took a little more work, but I believe the patch in r30798 (based on yours) completes the job. FWIW: the "hetero-nodes" flag is a bit of

Re: [OMPI users] map-by node with openmpi-1.7.5a1

Hi Ralph, I've found the fix. Please check the attached patch file. At this moment, nodes in hostfile should be listed in ascending order of slot size when we use "map-by node" or "map-by obj:span". The problem is that the hostfile created by Torque in our cluster always lists allocated nodes

[OMPI users] map-by node with openmpi-1.7.5a1

Hi Ralph, I did overall verification of rr_mapper, and I found another problem with "map-by node". As far as I checked, "map-by obj" other than node worked fine. I myself do not use "map-by node", but I'd like to report it to improve reliability of 1.7.5. It seems too difficult for me to resolve