[mvapich-discuss] Announcing the release of MVAPICH2 1.0-beta
Mike Houston
mhouston at graphics.stanford.edu
Mon Aug 13 18:55:04 EDT 2007
Nevermind, I was building a slightly older version I guess. Grabbing
from SVN seems to build clean for me. Now onto multi-threaded testing....
Thanks!
-Mike
Mike Houston wrote:
> I just grabbed the tarball and now hit problems with the same line of
> code:
>
> ch3_read_progress.c: In function `MPIDI_CH3I_read_progress':
> ch3_read_progress.c:146: error: too many arguments to function
> `MPIDI_CH3I_MRAILI_Cq_poll'
>
>
> Dhabaleswar Panda wrote:
>> Hi Eric,
>> We have fixed these problems. Please feel free to download the latest
>> version of the code from the trunk (either through svn checkout or the
>> nightly tarball being generated from the trunk .... changes will be
>> reflected in tonight's tarball). Web links to these are available on
>> the mvapich2 download page.
>>
>> Let us know if you experience any additional problems.
>>
>> Thanks,
>> DK
>>
>>
>>> Dr. Panda,
>>>
>>> Thank you again for you and your group's hard work on this software.
>>>
>>> I'll start by saying that I know I should move over to OpenFabrics
>>> and Gen2,
>>> but as we've discussed previously, this isn't currently a viable
>>> option for
>>> reasons that are outside the scope of this forum. With that said...
>>>
>>> A few compilation snags with MVAPICH2-1.0-beta on the VAPI flavor:
>>>
>>> (1) In src/mpid/osu_ch3/channels/mrail/src/rdma/ch3_read_progress.c
>>> line 146
>>> :
>>>
>>> type = MPIDI_CH3I_MRAILI_Cq_poll(v_ptr, NULL, 0, is_blocking)
>>>
>>> calls with four arguments; the VAPI version ( defined in
>>> src/mpid/osu_ch3/channels/mrail/src/vapi/mpidi_ch3_rdma_post.h ) has
>>> only
>>> the first three arguments. I imagine this is just a missing #ifdef
>>> switch
>>> ...
>>>
>>> (2) in src/mpid/osu_ch3/channels/mrail/src/vapi/rdma_iba_1sc.c lines
>>> 151-156
>>> :
>>>
>>> if (SMP_INIT)
>>> {
>>> /*correspoding post has not been issued */
>>> flag = 0;
>>> break;
>>> }
>>>
>>> These lines appear to have migrated here from somewhere else in the
>>> code
>>> (perhaps the function immediately above it.) The variable flag is
>>> undefined
>>> at this point, and there's a break statement without a loop to break
>>> out
>>> of...
>>>
>>> By no means a tested fix, but removing the last argument from the issue
>>> mentioned in (1) and commenting out the offending lines in (2)
>>> appears to
>>> allow the VAPI channel to compile and run (benchmarks, in-house tools)
>>> successfully. I haven't been able to get logging working, but that is
>>> another discussion.
>>>
>>> Your thoughts?
>>>
>>> Thanks again!
>>> Eric Borisch
>>>
>>> On 7/26/07, Dhabaleswar Panda <panda at cse.ohio-state.edu> wrote:
>>>
>>>> The MVAPICH team is pleased to announce the availability of
>>>> MVAPICH2-1.0-beta with the following NEW features:
>>>>
>>>> - Message coalescing support to enable reduction of per Queue-pair
>>>> send queues for reduction in memory requirement on large scale
>>>> clusters. This design also increases the small message messaging
>>>> rate significantly. Available for Open Fabrics Gen2-IB.
>>>>
>>>> - Hot-Spot Avoidance Mechanism (HSAM) for alleviating
>>>> network congestion in large scale clusters. Available for
>>>> Open Fabrics Gen2-IB.
>>>>
>>>> - RDMA CM based on-demand connection management for large scale
>>>> clusters. Available for OpenFabrics Gen2-IB and Gen2-iWARP.
>>>>
>>>> - uDAPL on-demand connection management for large scale clusters.
>>>> Available for uDAPL interface (including Solaris IB implementation).
>>>>
>>>> - RDMA Read support for increased overlap of computation and
>>>> communication. Available for OpenFabrics Gen2-IB and Gen2-iWARP.
>>>>
>>>> - Application-initiated system-level (synchronous) checkpointing in
>>>> addition to the user-transparent checkpointing. User application can
>>>> now request a whole program checkpoint synchronously with BLCR by
>>>> calling special functions within the application. Available for
>>>> OpenFabrics Gen2-IB.
>>>>
>>>> - Network-Level fault tolerance with Automatic Path Migration (APM)
>>>> for tolerating intermittent network failures over InfiniBand.
>>>> Available for OpenFabrics Gen2-IB.
>>>>
>>>> - Integrated multi-rail communication support for OpenFabrics
>>>> Gen2-iWARP.
>>>>
>>>> - Blocking mode of communication progress. Available for OpenFabrics
>>>> Gen2-IB.
>>>>
>>>> - Based on MPICH2 1.0.5p4.
>>>>
>>>> For downloading MVAPICH2 1.0-beta source code, associated user guide
>>>> and accessing the anonymous SVN, please visit the following URL:
>>>>
>>>> http://mvapich.cse.ohio-state.edu
>>>>
>>>> All feedbacks, including bug reports and hints for performance tuning,
>>>> are welcome. Please post it to the mvapich-discuss mailing list.
>>>>
>>>> Thanks,
>>>>
>>>> MVAPICH Team
>>>>
>>>> _______________________________________________
>>>> mvapich-discuss mailing list
>>>> mvapich-discuss at cse.ohio-state.edu
>>>> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>>>>
>>>>
>>> --
>>> Eric A. Borisch
>>> eborisch at ieee.org
>>>
>>> ------=_Part_46971_9804973.1185892355266
>>> Content-Type: text/html; charset=ISO-8859-1
>>> Content-Transfer-Encoding: 7bit
>>> Content-Disposition: inline
>>>
>>> Dr. Panda,<br><br>Thank you again for you and your group's hard
>>> work on this software.<br><br>I'll start by saying that I know I
>>> should move over to OpenFabrics and Gen2, but as we've discussed
>>> previously, this isn't currently a viable option for reasons
>>> that are outside the scope of this forum. With that said...
>>> <br><br>A few compilation snags with MVAPICH2-1.0-beta on the VAPI
>>> flavor:<br><br>(1) In
>>> src/mpid/osu_ch3/channels/mrail/src/rdma/ch3_read_progress.c line
>>> 146 :<br><br><div style="margin-left: 40px; font-family: courier
>>> new,monospace;">
>>> type = MPIDI_CH3I_MRAILI_Cq_poll(v_ptr, NULL, 0,
>>> is_blocking)<br></div><br>calls with four arguments; the VAPI
>>> version ( defined in
>>> src/mpid/osu_ch3/channels/mrail/src/vapi/mpidi_ch3_rdma_post.h ) has
>>> only the first three arguments. I imagine this is just a missing
>>> <span style="font-family: courier new,monospace;">#ifdef</span>
>>> switch ...<br><br>(2) in
>>> src/mpid/osu_ch3/channels/mrail/src/vapi/rdma_iba_1sc.c lines
>>> 151-156 : <br><br style="font-family: courier new,monospace;"><div
>>> style="margin-left: 40px;">
>>> <span style="font-family: courier new,monospace;">if
>>> (SMP_INIT)</span><br style="font-family: courier
>>> new,monospace;"><span style="font-family: courier
>>> new,monospace;">{</span><br style="font-family: courier
>>> new,monospace;">
>>> <span style="font-family: courier new,monospace;">
>>> /*correspoding post has not been issued */</span><br
>>> style="font-family: courier new,monospace;"><span
>>> style="font-family: courier new,monospace;"> flag
>>> = 0;</span>
>>> <br style="font-family: courier new,monospace;"><span
>>> style="font-family: courier new,monospace;">
>>> break;</span><br style="font-family: courier new,monospace;"><span
>>> style="font-family: courier new,monospace;">}</span>
>>> <br></div><br> These lines appear to have migrated here from
>>> somewhere else in the code (perhaps the function
>>> immediately above it.) The variable <span style="font-family:
>>> courier new,monospace;">flag</span> is undefined at this point, and
>>> there's a <span style="font-family: courier
>>> new,monospace;">break</span> statement without a loop to break out
>>> of...<br><br>By no means a tested fix, but removing the last
>>> argument from the issue mentioned in (1) and commenting out the
>>> offending lines in (2) appears to allow the VAPI channel to compile
>>> and run (benchmarks, in-house tools) successfully. I haven't
>>> been able to get logging working, but that is another discussion.
>>> <br><br>Your thoughts?<br><br>Thanks again!<br> Eric
>>> Borisch<br><br>On 7/26/07, Dhabaleswar Panda <<a
>>> href="mailto:panda at cse.ohio-state.edu">panda at cse.ohio-state.edu</a>>
>>> wrote:<br>> The MVAPICH team is pleased to announce the
>>> availability of
>>> <br>> MVAPICH2-1.0-beta with the following NEW features:<br>>
>>> <br>> - Message coalescing support to enable reduction of per
>>> Queue-pair<br>> send queues for reduction in memory
>>> requirement on large scale<br>> clusters. This design
>>> also increases the small message messaging
>>> <br>> rate significantly. Available for Open Fabrics
>>> Gen2-IB.<br>> <br>> - Hot-Spot Avoidance Mechanism (HSAM) for
>>> alleviating<br>> network congestion in large scale
>>> clusters. Available for<br>> Open Fabrics Gen2-IB.
>>> <br>> <br>> - RDMA CM based on-demand connection management
>>> for large scale<br>> clusters. Available for
>>> OpenFabrics Gen2-IB and Gen2-iWARP.<br>> <br>> - uDAPL
>>> on-demand connection management for large scale clusters.
>>> <br>> Available for uDAPL interface (including
>>> Solaris IB implementation).<br>> <br>> - RDMA Read support for
>>> increased overlap of computation and<br>>
>>> communication. Available for OpenFabrics Gen2-IB and Gen2-iWARP.
>>> <br>> <br>> - Application-initiated system-level (synchronous)
>>> checkpointing in<br>> addition to the
>>> user-transparent checkpointing. User application
>>> can<br>> now request a whole program checkpoint
>>> synchronously with BLCR by
>>> <br>> calling special functions within the
>>> application. Available for<br>> OpenFabrics
>>> Gen2-IB.<br>> <br>> - Network-Level fault tolerance with
>>> Automatic Path Migration (APM)<br>> for tolerating
>>> intermittent network failures over InfiniBand.
>>> <br>> Available for OpenFabrics Gen2-IB.<br>>
>>> <br>> - Integrated multi-rail communication support for
>>> OpenFabrics<br>> Gen2-iWARP.<br>> <br>> -
>>> Blocking mode of communication progress. Available for OpenFabrics
>>> <br>> Gen2-IB.<br>> <br>> - Based on MPICH2
>>> 1.0.5p4.<br>> <br>> For downloading MVAPICH2 1.0-beta source
>>> code, associated user guide<br>> and accessing the anonymous SVN,
>>> please visit the following URL:
>>> <br>> <br>> <a
>>> href="http://mvapich.cse.ohio-state.edu">http://mvapich.cse.ohio-state.edu</a><br>>
>>> <br>> All feedbacks, including bug reports and hints for
>>> performance tuning,<br>> are welcome. Please post it to the
>>> mvapich-discuss mailing list.
>>> <br>> <br>> Thanks,<br>> <br>> MVAPICH Team<br>>
>>> <br>> _______________________________________________<br>>
>>> mvapich-discuss mailing list<br>> <a
>>> href="mailto:mvapich-discuss at cse.ohio-state.edu">mvapich-discuss at cse.ohio-state.edu
>>>
>>> </a><br>> <a
>>> href="http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss">http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss</a><br>>
>>> <br><br><br>-- <br>Eric A. Borisch<br><a
>>> href="mailto:eborisch at ieee.org">
>>> eborisch at ieee.org</a><br><br>
>>>
>>> ------=_Part_46971_9804973.1185892355266--
>>>
>>>
>>
>> _______________________________________________
>> mvapich-discuss mailing list
>> mvapich-discuss at cse.ohio-state.edu
>> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>>
>>
> _______________________________________________
> mvapich-discuss mailing list
> mvapich-discuss at cse.ohio-state.edu
> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>
More information about the mvapich-discuss
mailing list