<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18852"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=546022918-13112009><FONT color=#0000ff
size=2 face=Arial>If you use the default Nemesis channel (ch3:nemesis),
communication within a node goes over shared memory and across nodes over some
communication channel.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=546022918-13112009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=546022918-13112009><FONT color=#0000ff
size=2 face=Arial>Rajeev</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> mpich-discuss-bounces@mcs.anl.gov
[mailto:mpich-discuss-bounces@mcs.anl.gov] <B>On Behalf Of </B>hu
yaohui<BR><B>Sent:</B> Friday, November 13, 2009 3:13 AM<BR><B>To:</B>
mpich-discuss@mcs.anl.gov<BR><B>Subject:</B> Re: [mpich-discuss]答复: how to
connect MPI_Send with CH3_isend<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>thank you very much!</DIV>
<DIV> I would really appreciate,if you can give me some
detail steps from the implemention of these functions to deploy
the mpich2 on my clusters! (such as how to modify the configure
file sth like that.)</DIV>
<DIV> i did a test yesterday ,i install the mpich2 three
times ,and then check the make
output,chosse ./configure --with-device=ch3:sock,--with-device=ch3:sctp
and default,</DIV>
<DIV>does these device means the internode communication channel? and the
default intranode communication channel is shared-memory and cann't be
modified?</DIV>
<DIV>
thank you very much!</DIV>
<DIV>
best wishes!<BR></DIV>
<DIV class=gmail_quote>2009/11/13 Darius Buntinas <SPAN dir=ltr><<A
href="mailto:buntinas@mcs.anl.gov">buntinas@mcs.anl.gov</A>></SPAN><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote><BR>The ability to use different networks for
different<BR>destinations is a feature we intend to add, but it's not<BR>yet
implemented. 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. 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're interested in porting MPICH2 to a new interconnect,<BR>you should
write a nemesis network module. 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>> Thank you very much!<BR>> Finally I
got a response!<BR>> I am doing some researches on adding
HT(HyperTransport) into mpich2,I am<BR>> just wandering when we configure
the mpich2 with<BR>>
./configure –with-device=ch3:sock
(ch3:nemesis)<BR>> that means we definitely select one network as the
channel to communicate,<BR>> but if there are any possibilities that you
can dynamic<BR>> control the network we use ,sometimes messages go
through Ethernet,<BR>> sometimes go through IB. could you give me some
materials<BR>> to understand what's the difference between
~/ch3/channel/sock<BR>> ,~/ch3/channel/sctp
~,~/ch3/channel/nemesis/nemesis/net_mod/tcp_module<BR>> ,
~/ch3/channel/nemesis/nemesis/net_mod/sctp_module,<BR>>
~/ch3/channel/nemesis/nemesis/net_mod/ib_module<BR>><BR>> Thank you
again!<BR>><BR>> Best Wishes!<BR>> -----邮件原件-----<BR>> 发件人: <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>>
<A href="http://anl.gov/" target=_blank>anl.gov</A>] 代表 Darius
Buntinas<BR>> 发送时间: 2009年11月12日 23:30<BR>> 收件人: <A
href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</A><BR>>
主题: Re: [mpich-discuss] how to connect MPI_Send with
CH3_isend<BR>><BR>> The best way to understand what happens is to step
through the calls<BR>> with a debugger. The channel is selected in
the configure step, and<BR>> only that channel will be compiled, so there
will be only one copy of<BR>> ch3_isend in the binary.<BR>><BR>>
-d<BR>><BR>> On 11/12/2009 05:54 AM, hu yaohui wrote:<BR>>> hi
guys!<BR>>> Could someone tell me the detail calling
flow from MPI_Send() to<BR>>> CH3_isend()?<BR>>>
How to control which CH3_isend() is called between sock,sctp and<BR>>>
shm? thank you very much!<BR>>><BR>> best<BR>>>
wishes!<BR>>><BR>><BR>>>
loki!<BR>>><BR>>><BR>>><BR>>>
------------------------------------------------------------------------<BR>>><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>> 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>><BR>><BR>>
------------------------------------------------------------------------<BR>><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></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></BLOCKQUOTE></BODY></HTML>