On 06/29/15 17:25, Nathan Hjelm wrote:
This is not a configuration issue. On 1.8.x and master we use two-sided communication to emulation one-sided. Since we do not currently have async progress this requires the target to call into MPI to progress RMA communication.This will change in 2.x. I will be adding a new component that does real RMA on supported networks (ib, gemini, aries). At some point we will also have support for async progress which will enable passive-target on other networks.
But isn't aynch progress required for MPI 2.x conformance? The Open MPI 1.6.5 headers I have #define MPI_VERSION to 2. The 1.8.4 headers I have even define it to 3. Why isn't a background thread used on platforms that don't have supported networks?
Thomas
smime.p7s
Description: S/MIME Cryptographic Signature
