Re: [OMPI devel] Upgrading our (openSUSE) Open MPI version

2016-08-24 Thread Gilles Gouaillardet
Karol, i was able to build openmpi 1.10.3 and run simple programs on tumbleweed with updated glibc (2.24-436.59) i downloaded from http://download.opensuse.org/repositories/Base:/System/openSUSE_Factory/x86_64/ would you mind describing the issue you faced with the updated glibc and openmp

[OMPI devel] [2.0.1rc1] minor nits in README

2016-08-24 Thread Paul Hargrove
A run of "spell README" produces (after manual filtering) the following misspelled words: appliation applicaions availble compatibile libeveny Memopy paramater relavant specfic It appears that us middleware authors don't know how to write "applications" ;-) README says: - Open MPI's run-time

Re: [OMPI devel] OMPI v2.0.1rc1 available for test

2016-08-24 Thread Gilles Gouaillardet
If my git is correct $ git rev-list --boundary v2.x...master/master | grep '^-' -acc2c7937cd3b50de16044b673399e4c4a7456bc -6772d32b85b836438eeca72e4a8fda026ea67a55 -ec44a25070f99b6e1d96886fe3990ad560ee63c0 $ git show ec44a25070f99b6e1d96886fe3990ad560ee63c0 commit ec44a25070f99b6e1d96886fe3990a

Re: [OMPI devel] OMPI v2.0.1rc1 available for test

2016-08-24 Thread Sreenidhi Bharathkar Ramesh via devel
Hi, With respect to "master" branch, from which commit is v2.0.1 branched off ? Please let me know. Thanks, - Sreenidhi. On Tue, Aug 23, 2016 at 2:59 AM, r...@open-mpi.org wrote: > Hello folks > > Dunno where the head-honcho’s are hiding, but per their request: the newest > v2.0.1 release cand

Re: [OMPI devel] Binding with --oversubscribe in 2.0.0

2016-08-24 Thread r...@open-mpi.org
Okay, I found the issue and fixed it: https://github.com/open-mpi/ompi-release/pull/1340 We are very close to v2.0.1 release, so it may not get into that one. Still, you are welcome to pull down the patch and locally apply it if it would help. Ralph > On Aug 24, 2016, at 5:29 PM, r...@open-mpi

Re: [OMPI devel] [2.0.1.rc1] Solaris MPIX failure

2016-08-24 Thread Paul Hargrove
My previous response was composed too quickly. I should have said "successfully built and RUN". -Paul On Wed, Aug 24, 2016 at 9:04 PM, Gilles Gouaillardet wrote: > Thanks Paul ! > > > yes, this snapshot does include the patch i posted earlier. > > btw, the issue was a runtime error, not a buil

Re: [OMPI devel] [2.0.1.rc1] Solaris MPIX failure

2016-08-24 Thread Gilles Gouaillardet
Thanks Paul ! yes, this snapshot does include the patch i posted earlier. btw, the issue was a runtime error, not a build error. Cheers, Gilles On 8/25/2016 12:00 PM, Paul Hargrove wrote: Giles, I have successfully built openmpi-v2.0.0-227-g917d293 (tonight's nightly tarball) on Solari

Re: [OMPI devel] [2.0.1.rc1] Solaris MPIX failure

2016-08-24 Thread Paul Hargrove
Giles, I have successfully built openmpi-v2.0.0-227-g917d293 (tonight's nightly tarball) on Solaris 11.3 with both the Gnu and Studio compilers. Based on Ralph's previous email, I assume that included the patch you had directed me to (though I did not attempt to verify that myself). -Paul On We

Re: [OMPI devel] Upgrading our (openSUSE) Open MPI version

2016-08-24 Thread Gilles Gouaillardet
Karol, is there any place i can download glibc 2.24 for tumbleweed ? i'd like to have a look at what is going wrong with openmpi 1.10 Cheers, Gilles On 8/25/2016 10:24 AM, Karol Mroz wrote: Greetings! I would like to upgrade our (openSUSE Tumbleweed) version of Open MPI from 1.10.3 to

Re: [OMPI devel] Upgrading our (openSUSE) Open MPI version

2016-08-24 Thread Karol Mroz
Hi Gilles, Thanks for the speedy reply. I'm using our existing spec file. Tumbleweed is meant to be a rolling distribution, so I think 2.0.0 fits well. I can always upgrade the package when 2.0.1 comes out. For our Leap distribution, a more mature 1.10.x fits. Thanks for confirming VT is out of

Re: [OMPI devel] Upgrading our (openSUSE) Open MPI version

2016-08-24 Thread Gilles Gouaillardet
Karol, it is correct vampirtrace was removed from Open MPI 2.0.0 are you using your own (or openSUSE) .spec file ? or the one provided by Open MPI ? fwiw, Open MPI 1.10.4 and 2.0.1 should be released in a near future. Cheers, Gilles On 8/25/2016 10:24 AM, Karol Mroz wrote: Greetings!

[OMPI devel] Upgrading our (openSUSE) Open MPI version

2016-08-24 Thread Karol Mroz
Greetings! I would like to upgrade our (openSUSE Tumbleweed) version of Open MPI from 1.10.3 to the shiny new 2.0.0 :) This is motivated by a number of factors, including an upgrade to glibc2.24 which breaks our current build of Open MPI. I thought it a great time to push out a new version :D The

Re: [OMPI devel] Binding with --oversubscribe in 2.0.0

2016-08-24 Thread r...@open-mpi.org
Hmmm...bet I know why. Let me poke a bit. > On Aug 24, 2016, at 5:18 PM, Ben Menadue wrote: > > Actually, adding :oversubscribe to the --map-by option still disables > binding, even with :overload on the --bind-to option. While the :overload > option allows binding more than one process per CP

Re: [OMPI devel] Binding with --oversubscribe in 2.0.0

2016-08-24 Thread Ben Menadue
Actually, adding :oversubscribe to the --map-by option still disables binding, even with :overload on the --bind-to option. While the :overload option allows binding more than one process per CPU, it only has an effect if binding actually happens - i.e. without :oversubscribe. So, on one of our

Re: [OMPI devel] Binding with --oversubscribe in 2.0.0

2016-08-24 Thread r...@open-mpi.org
Yeah, that man page could use some work...will add it to the list. > On Aug 24, 2016, at 4:35 PM, Ben Menadue wrote: > > Hi Ralph, > > Thanks for that... that option's not on the man page for mpirun, but I can > see it in the --help message (as "overload-allowed", which also works). > > Cheer

Re: [OMPI devel] Binding with --oversubscribe in 2.0.0

2016-08-24 Thread Ben Menadue
Hi Ralph, Thanks for that... that option's not on the man page for mpirun, but I can see it in the --help message (as "overload-allowed", which also works). Cheers, Ben -Original Message- From: devel [mailto:devel-boun...@lists.open-mpi.org] On Behalf Of r...@open-mpi.org Sent: Thursd

Re: [OMPI devel] [2.0.1.rc1] Solaris MPIX failure

2016-08-24 Thread Paul Hargrove
Ralph, That will allow me to test much sooner. -Paul On Wed, Aug 24, 2016 at 10:41 AM, r...@open-mpi.org wrote: > When you do, that PR has already been committed, so you can just pull the > next nightly 2.x tarball and test from there > > On Aug 24, 2016, at 10:39 AM, Paul Hargrove wrote: > >

Re: [OMPI devel] [2.0.1.rc1] Solaris MPIX failure

2016-08-24 Thread r...@open-mpi.org
When you do, that PR has already been committed, so you can just pull the next nightly 2.x tarball and test from there > On Aug 24, 2016, at 10:39 AM, Paul Hargrove wrote: > > I am afraid it might take a day or two before I can get to testing that patch. > > -Paul > > On Tue, Aug 23, 2016 at

Re: [OMPI devel] [2.0.1.rc1] Solaris MPIX failure

2016-08-24 Thread Paul Hargrove
I am afraid it might take a day or two before I can get to testing that patch. -Paul On Tue, Aug 23, 2016 at 10:16 PM, Gilles Gouaillardet wrote: > Paul, > > > you can download a patch at https://patch-diff.githubusercontent.com/raw/ > open-mpi/ompi-release/pull/1336.patch > > (note you need re

Re: [OMPI devel] Binding with --oversubscribe in 2.0.0

2016-08-24 Thread r...@open-mpi.org
Actually, I stand corrected! Someone must have previously requested it, because support already exists. What you need to do is simply specify the desired binding. If you don’t specify one, then we will disable it by default when oversubscribed. This was done to protect performance for those who

[OMPI devel] OMPI v1.10.4

2016-08-24 Thread r...@open-mpi.org
Hi folks Looks like we will need to release a 1.10.4 to pickup a desired patch, and so I plan to do so next week (week of Aug 29th). I know of one issue I’ve heard about - please let me know if there are any others, and/or if someone wants any additional changes in it. There are two outstanding

Re: [OMPI devel] Binding with --oversubscribe in 2.0.0

2016-08-24 Thread r...@open-mpi.org
Well, that’s a new one! I imagine we could modify the logic to allow a combination of oversubscribe and overload flags. Won’t get out until 2.1, though you could pull the patch in advance if it is holding you up. > On Aug 23, 2016, at 11:46 PM, Ben Menadue wrote: > > Hi, > > One of our users