thank you very much!<br><br>
<div class="gmail_quote">2009/11/13 Darius Buntinas <span dir="ltr">&lt;<a href="mailto:buntinas@mcs.anl.gov">buntinas@mcs.anl.gov</a>&gt;</span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>The ability to use different networks for different<br>destinations is a feature we intend to add, but it&#39;s not<br>
yet implemented. &nbsp;Nemesis does use shared-memory communication<br>for intranode communication and the network for internode.<br><br>There are several internal interfaces for porting MPICH2 to new<br>platforms or interconnects. &nbsp;This paper has a description of the<br>
interfaces:<br><a href="http://www.mcs.anl.gov/~buntinas/papers/europvmmpi06-nemesis.pdf" target="_blank">http://www.mcs.anl.gov/~buntinas/papers/europvmmpi06-nemesis.pdf</a><br><br>If you&#39;re interested in porting MPICH2 to a new interconnect,<br>
you should write a nemesis network module. &nbsp;The API is described<br>here:<br><a href="http://wiki.mcs.anl.gov/mpich2/index.php/Nemesis_Network_Module_API" target="_blank">http://wiki.mcs.anl.gov/mpich2/index.php/Nemesis_Network_Module_API</a><br>
<br>I hope this helps,<br><font color="#888888"><br>-d<br></font>
<div>
<div></div>
<div class="h5"><br><br><br><br><br><br>On 11/12/2009 11:29 PM, yaohui wrote:<br>&gt; Thank you very much!<br>&gt; &nbsp; &nbsp; &nbsp; Finally I got a response!<br>&gt; I am doing some researches on adding HT(HyperTransport) into mpich2,I am<br>
&gt; just wandering when we configure the mpich2 with<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ./configure &ndash;with-device=ch3:sock (ch3:nemesis)<br>&gt; that means we definitely select one network as the channel to communicate,<br>&gt; but if there are any possibilities that you can dynamic<br>
&gt; control the network we use ,sometimes messages go through Ethernet,<br>&gt; sometimes go through IB. could you give me some materials<br>&gt; to understand what&#39;s the difference between ~/ch3/channel/sock<br>&gt; ,~/ch3/channel/sctp ~,~/ch3/channel/nemesis/nemesis/net_mod/tcp_module<br>
&gt; , ~/ch3/channel/nemesis/nemesis/net_mod/sctp_module,<br>&gt; ~/ch3/channel/nemesis/nemesis/net_mod/ib_module<br>&gt;<br>&gt; Thank you again!<br>&gt;<br>&gt; Best Wishes!<br>&gt; -----邮件原件-----<br>&gt; 发件人: <a href="mailto:mpich-discuss-bounces@mcs.anl.gov">mpich-discuss-bounces@mcs.anl.gov</a> [mailto:<a href="mailto:mpich-discuss-bounces@mcs">mpich-discuss-bounces@mcs</a>.<br>
&gt; <a href="http://anl.gov/" target="_blank">anl.gov</a>] 代表 Darius Buntinas<br>&gt; 发送时间: 2009年11月12日 23:30<br>&gt; 收件人: <a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br>&gt; 主题: Re: [mpich-discuss] how to connect MPI_Send with CH3_isend<br>
&gt;<br>&gt; The best way to understand what happens is to step through the calls<br>&gt; with a debugger. &nbsp;The channel is selected in the configure step, and<br>&gt; only that channel will be compiled, so there will be only one copy of<br>
&gt; ch3_isend in the binary.<br>&gt;<br>&gt; -d<br>&gt;<br>&gt; On 11/12/2009 05:54 AM, hu yaohui wrote:<br>&gt;&gt; hi guys!<br>&gt;&gt; &nbsp; &nbsp; Could someone tell me the detail calling flow from MPI_Send() to<br>&gt;&gt; CH3_isend()?<br>
&gt;&gt; &nbsp; &nbsp; How to control which CH3_isend() is called between sock,sctp and<br>&gt;&gt; shm? thank you very much!<br>&gt;&gt;<br>&gt; best<br>&gt;&gt; wishes!<br>&gt;&gt;<br>&gt;<br>&gt;&gt; loki!<br>&gt;&gt;<br>&gt;&gt;<br>
&gt;&gt;<br>&gt;&gt; ------------------------------------------------------------------------<br>&gt;&gt;<br>&gt;&gt; _______________________________________________<br>&gt;&gt; mpich-discuss mailing list<br>&gt;&gt; <a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br>
&gt;&gt; <a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>&gt; _______________________________________________<br>&gt; mpich-discuss mailing list<br>
&gt; <a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br>&gt; <a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
&gt;<br>&gt;<br>&gt;<br>&gt; ------------------------------------------------------------------------<br>&gt;<br>&gt; _______________________________________________<br>&gt; mpich-discuss mailing list<br>&gt; <a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br>
&gt; <a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br></div></div><br>_______________________________________________<br>mpich-discuss mailing list<br>
<a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br><a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
<br></blockquote></div><br>