Tom -- If you're going to upgrade, can you upgrade to the latest Open MPI (2.1.1)? I.e., unless you have a reason for wanting to stay back at an already-old version, you might as well upgrade to the latest latest latest to give you the longest shelf life.
I mention this because we are immanently about to release Open MPI v3.0.0, which will knock v1.10.x into the "unsupported" category (i.e., we'll be supporting v3.0.x, v2.1.x, and v2.0.x). All that being said: if you need to stay back at the 1.10 series for some reason, you should update to the latest 1.10.x: v1.10.7 (not v1.10.5). > On Sep 8, 2017, at 10:10 AM, r...@open-mpi.org wrote: > > What you probably want to do is add --cpu-list a,b,c... to each mpirun > command, where each one lists the cores you want to assign to that job. > > >> On Sep 8, 2017, at 6:46 AM, twu...@goodyear.com wrote: >> >> >> I posted this question last year and we ended up not upgrading to the newer >> openmpi. Now I need to change to openmpi 1.10.5 and have the same issue. >> >> Specifically, using 1.4.2, I can run two 12 core jobs on a 24 core node and >> the >> processes would bind to cores and only have 1 process per core. ie not >> oversubscribe. >> >> What I used with 1.4.2 was: >> mpirun --mca mpi_paffinity_alone 1 --mca btl openib,tcp,sm,self ... >> >> Now with 1.10.5, I have tried multiple combinations of map-to core, bind-to >> core >> etc and cannot run 2 jobs on the same node without oversubcribing. >> >> Is there a solution to this? >> >> Thanks for any info >> tom >> _______________________________________________ >> users mailing list >> users@lists.open-mpi.org >> https://lists.open-mpi.org/mailman/listinfo/users > > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/users -- Jeff Squyres jsquy...@cisco.com _______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
