Re: [OMPI devel] mca_mtl_psm and java

Sorry - but there are some discussions that cannot and should not take place on a public mailing list. As a former corporate person yourself, you should understand :-) > On Aug 25, 2015, at 6:56 PM, Howard Pritchard wrote: > > which off-list are we talking about? > very annoying. > > > 2015-

Re: [OMPI devel] mca_mtl_psm and java

which off-list are we talking about? very annoying. 2015-08-25 10:38 GMT-06:00 Ralph Castain : > We’re looking at this off-list. It would be preferable not to disable PSM > if we can avoid it > > On Aug 25, 2015, at 9:32 AM, Nathaniel Graham > wrote: > > What if we modify the mpirun script to i

Re: [OMPI devel] mca_mtl_psm and java

Thanks Paul, I will give it a try Cheers, Gilles On Wednesday, August 26, 2015, Paul Hargrove wrote: > Gilles, > > Is the conflict over "SIG32"? > If so, I believe setenv PSM_RCVTHREAD=0 in the environment will disable > InfiniPath's use of that signal. > > -Paul > > On Tue, Aug 25, 2015 at 6

Re: [OMPI devel] mca_mtl_psm and java

Gilles, Is the conflict over "SIG32"? If so, I believe setenv PSM_RCVTHREAD=0 in the environment will disable InfiniPath's use of that signal. -Paul On Tue, Aug 25, 2015 at 6:02 PM, Gilles Gouaillardet < gilles.gouaillar...@gmail.com> wrote: > i run on a centos 7 vm, and with the OFED that come

Re: [OMPI devel] cosmetic misleading mpirun error message

would it be easier if the option was --host instead of -host ? I guess changing the cli is not an option for the v1.x series, so what about adding the -hosts option (alias to -host option) ? I made the same mistake a few times before, adding a s to hosts looks more intuitive for me. my 0.02 US$ Gi

Re: [OMPI devel] mca_mtl_psm and java

i run on a centos 7 vm, and with the OFED that comes with centos (I will send full details tomorrow) there is no psm hardware, just infinipath libs a first trivial workaround in ompi would be to putenv("OMPI_MCA_mtl_psm_priority=0") in the java binding before invoking ompi_mpi_init, but that canno

Re: [OMPI devel] fortran calling MPI_* instead of PMPI_*

On Aug 25, 2015, at 11:03 AM, George Bosilca wrote: > > This seems to be the case only with the TKR interface. All the others are > either calling the OMPI version directly (mpif-h), or are calling some other > internal (or weak symbol function). Yes, those might need to be updated. Not it!

Re: [OMPI devel] cosmetic misleading mpirun error message

Fair point. I don't know if there's an easy way to fix that, though. > On Aug 25, 2015, at 6:01 PM, Cabral, Matias A > wrote: > > Hi, > > > > Playing with the 1.10.0 (just released) build I found a cosmetic misleading > error message in mpirun. If by mistake you type -hosts (with an extr

[OMPI devel] cosmetic misleading mpirun error message

Hi, Playing with the 1.10.0 (just released) build I found a cosmetic misleading error message in mpirun. If by mistake you type -hosts (with an extra "s"), the error message complains about an unknown "-o" option that is actually not being used. Typing the parameters correctly fixes the issue

Re: [OMPI devel] mca_mtl_psm and java

Gilles: what version of PSM were you using? and with which cards? > On Aug 25, 2015, at 9:32 AM, Nathaniel Graham wrote: > > What if we modify the mpirun script to include the --mca mtl ^psm tag if java > is in the run string? > > -Nathan > > On Tue, Aug 25, 2015 at 9:47 AM, Howard Pritchard

Re: [OMPI devel] mca_mtl_psm and java

We’re looking at this off-list. It would be preferable not to disable PSM if we can avoid it > On Aug 25, 2015, at 9:32 AM, Nathaniel Graham wrote: > > What if we modify the mpirun script to include the --mca mtl ^psm tag if java > is in the run string? > > -Nathan > > On Tue, Aug 25, 2015 a

Re: [OMPI devel] mca_mtl_psm and java

What if we modify the mpirun script to include the --mca mtl ^psm tag if java is in the run string? -Nathan On Tue, Aug 25, 2015 at 9:47 AM, Howard Pritchard wrote: > I'll update the java FAQ. > > 2015-08-25 8:36 GMT-06:00 Jeff Squyres (jsquyres) : > >> On Aug 25, 2015, at 10:00 AM, Howard Prit

Re: [OMPI devel] v1.10.0rc7

Thanks Paul!! > On Aug 24, 2015, at 11:46 PM, Paul Hargrove wrote: > > With only the slow qemu-emulated MIPS and ARM testers still running, I can > report that I have seen NO issues with rc7. > > -Paul > > On Mon, Aug 24, 2015 at 4:54 PM, Ralph Castain > wrote: > Ye

Re: [OMPI devel] mca_mtl_psm and java

I'll update the java FAQ. 2015-08-25 8:36 GMT-06:00 Jeff Squyres (jsquyres) : > On Aug 25, 2015, at 10:00 AM, Howard Pritchard > wrote: > > > > I think rather than trying workarounds of dubious robustness inside open > mpi we > > > > - dicument the issue on either the somewhat aged open mpi webs

Re: [OMPI devel] fortran calling MPI_* instead of PMPI_*

This seems to be the case only with the TKR interface. All the others are either calling the OMPI version directly (mpif-h), or are calling some other internal (or weak symbol function). George. On Tue, Aug 25, 2015 at 9:04 AM, Bert Wesarg wrote: > On 08/25/2015 02:44 PM, Gilles Gouaillardet

Re: [OMPI devel] mca_mtl_psm and java

On Aug 25, 2015, at 10:00 AM, Howard Pritchard wrote: > > I think rather than trying workarounds of dubious robustness inside open mpi > we > > - dicument the issue on either the somewhat aged open mpi website faq or add > it to a wiki page on github It should probably be documented in the RE

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch master updated. dev-2362-ge2124c6

is this going in to v2.x? -- sent from my smart phonr so no good type. Howard On Aug 25, 2015 7:54 AM, wrote: > This is an automated email from the git hooks/post-receive script. It was > generated because a ref change was pushed to the repository containing > the project "open-mpi/omp

Re: [OMPI devel] mca_mtl_psm and java

I think rather than trying workarounds of dubious robustness inside open mpi we - dicument the issue on either the somewhat aged open mpi website faq or add it to a wiki page on github - file a bug against intel psm -- sent from my smart phonr so no good type. Howard On Aug 25, 2015 6:

Re: [OMPI devel] mca_mtl_psm and java

Intel folks: can you comment on this? It appears that the libinfinipath signal handler is interfering with the java garbage collector. > On Aug 25, 2015, at 8:01 AM, Gilles Gouaillardet > wrote: > > i do not know if this can be runtime detected ... > note we should report this to intel folks

Re: [OMPI devel] fortran calling MPI_* instead of PMPI_*

On 08/25/2015 02:44 PM, Gilles Gouaillardet wrote: Folks, I ran some basic tests with IPM profiler-like https://github.com/nerscadmin/IPM and found that when fortran calls an mpi subroutine, this is accounted twice. IPM defines both MPI_* subroutines and their fortran mpi_*_ counterpart. since t

[OMPI devel] fortran calling MPI_* instead of PMPI_*

Folks, I ran some basic tests with IPM profiler-like https://github.com/nerscadmin/IPM and found that when fortran calls an mpi subroutine, this is accounted twice. IPM defines both MPI_* subroutines and their fortran mpi_*_ counterpart. since the ompi fortran calls the MPI_* symbol (and not the P

Re: [OMPI devel] mca_mtl_psm and java

i do not know if this can be runtime detected ... note we should report this to intel folks and ask them to advise. ideally, they would provide a way to make sure libinfinipath.so does not conflict with the jvm signal handlers. my idea is to dlopen libinfinipath only if java bindings are not used.

Re: [OMPI devel] mca_mtl_psm and java

Is it possible to run-time detect this situation? E.g., probe the signal handler, or somesuch. Rationale: I'd rather have something run-time disabled than not built. Would dlopen'ing libinfinipath change actually change its signal handler behavior? > On Aug 25, 2015, at 4:27 AM, Gilles Gouai

Re: [OMPI devel] esslingen MTT?

+1 -- thanks Adrian. > On Aug 25, 2015, at 4:04 AM, Gilles Gouaillardet wrote: > > Thanks Adrian, > > i fixed this in PR #831 https://github.com/open-mpi/ompi/pull/831 and push it > shortly to master > > Best regards, > > Gilles > > On 8/25/2015 4:47 PM, Adrian Reber wrote: >> On Mon, Aug 2

[OMPI devel] mca_mtl_psm and java

Folks, some time ago, some crashes were reported when using java bindings. one of them was caused was caused by mca_mtl_psm.so. the root cause is libinfinipath.so initializer sets its own signal handler, which conflicts with the signal handler sets by the jvm. the only workaround is to disable

Re: [OMPI devel] esslingen MTT?

Thanks Adrian, i fixed this in PR #831 https://github.com/open-mpi/ompi/pull/831 and push it shortly to master Best regards, Gilles On 8/25/2015 4:47 PM, Adrian Reber wrote: On Mon, Aug 24, 2015 at 09:47:22PM +, Jeff Squyres (jsquyres) wrote: Who runs the esslingen MTT? You're getting

Re: [OMPI devel] esslingen MTT?

On Mon, Aug 24, 2015 at 09:47:22PM +, Jeff Squyres (jsquyres) wrote: > Who runs the esslingen MTT? > > You're getting some build failures on master that I don't understand: > > - > make[3]: Entering directory > '/home/adrian/mtt-scratch/mpi-install/FDvh/src/openmpi-dev-2350-geb25c00/ompi/

Re: [OMPI devel] v1.10.0rc7

With only the slow qemu-emulated MIPS and ARM testers still running, I can report that I have seen NO issues with rc7. -Paul On Mon, Aug 24, 2015 at 4:54 PM, Ralph Castain wrote: > Yet another step in the apparently never-ending quest to release v1.10.0… > > http://www.open-mpi.org/software/omp

Re: [OMPI devel] 1.10.0rc6 - slightly different mx problem

Le 25/08/2015 05:59, Christopher Samuel a écrit : > > INRIA does have Open-MX (Myrinet Express over Generic Ethernet > Hardware), last release December 2014. No idea if it's still developed > or used.. > > http://open-mx.gforge.inria.fr/ > > Brice? > > Open-MPI is listed as working with it there.