[mvapich-discuss] MVAPICH2 2.3b Blocking communication progress

Subramoni, Hari subramoni.1 at osu.edu
Fri Oct 20 15:01:45 EDT 2017


Hi, Pau.

To the best of our knowledge, the Intel PSM2 interface does not support interrupt driven mode of progress. We need to poll all the time to check for progress. So we cannot implement the traditional “blocking” mode of progress for Intel Omni-Path HFIs.

We had some discussions with Intel folks about this in the past. I am not sure about the current status. I would recommend contacting Intel PSM2 developers for more information.

Thx,
Hari.

From: mvapich-discuss-bounces at cse.ohio-state.edu On Behalf Of Pau Farré
Sent: Friday, October 20, 2017 1:50 PM
To: mvapich-discuss at cse.ohio-state.edu <mvapich-discuss at mailman.cse.ohio-state.edu>
Subject: [mvapich-discuss] MVAPICH2 2.3b Blocking communication progress


Hi,

I amb interested in using MVAPICH 2.3b with the blocking communication progress mode and Intel Omnipath.

Is this actually supported? Since on the list of features says:

  *   Blocking (enables running multiple MPI processes/processor). Available for OpenFabrics (IB and iWARP) interfaces.

Thanks,

Pau Farre


WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received.

http://www.bsc.es/disclaimer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 10508 bytes
Desc: not available
URL: <http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/attachments/20171020/78e61e83/attachment.bin>


More information about the mvapich-discuss mailing list