Re: [OMPI devel] OMPI devel] mpi_yield_when_idle=1 and still 100%CPU

2018-01-22 Thread Paul Kapinos
Gilles, a short update about the patched version (3.0.0). After we updated from CentOS 7.3 to 7.4, this version build with all versions of all compilers stopped to work with message like: $ a.out: symbol lookup error: /opt/MPI/openmpi-3.0.0p/linux/intel_17.0.5.239/lib/openmpi/mca_mpool_memkind.so:

Re: [OMPI devel] mpi_yield_when_idle=1 and still 100%CPU

2017-10-13 Thread Paul Kapinos
Good news everyone! PR #4331 works, I was able to apply it on 3.0.0-release (two hunks succeeded with a offset, and the line 65 in openmpi-3.0.0/ompi/runtime/ompi_mpi_params.c has to be changed > < bool ompi_mpi_yield_when_idle = true; > > bool ompi_mpi_yield_when_idle = false; prior pathing to ma

Re: [OMPI devel] OMPI devel] mpi_yield_when_idle=1 and still 100%CPU

2017-10-12 Thread Gilles Gouaillardet
Paul, Sorry for the typo. The patch was developed on the master branch. Note v1.10 is no more supported, and since passive wait is a new feature, it would start at v3.1 or later. That being said, if you are kind of stucked with 1.10.7, i can try to craft a one off patch in order to help Chee

Re: [OMPI devel] mpi_yield_when_idle=1 and still 100%CPU

2017-10-12 Thread Paul Kapinos
Hi Gilles, Thank you for your message and quick path! You likely mean (instead of links in your eMail below) https://github.com/open-mpi/ompi/pull/4331 and https://github.com/open-mpi/ompi/pull/4331.patch for your PR #4331 (note '4331' instead of '4431' :-) I was not able to path 1.10.7 release

Re: [OMPI devel] mpi_yield_when_idle=1 and still 100%CPU

2017-10-12 Thread Gilles Gouaillardet
Paul, i made PR #4331 https://github.com/open-mpi/ompi/pull/4431 in order to implement this. in order to enable passive wait, you simply need to mpirun --mca mpi_poll_when_idle true ... fwiw, when you use mpi_yield_when_idle, Open MPI does (highly oversimplified) for (...) sched_yield()

[OMPI devel] mpi_yield_when_idle=1 and still 100%CPU

2017-10-11 Thread Paul Kapinos
Dear Jeff, Dear All, we know about *mpi_yield_when_idle* parameter [1]. We read [2]. You're right, > if an MPI application is waiting a long time for messages, > perhaps its message passing algorithm should be re-designed ... but we cannot spur the ParaView/VTK developer to rewrite their software