<html><body>
<p>Why would JOIN be any less useful today than in the past? Why would you want to deprecate it? It is a trivial bootstrap for the simplest form of ACCEPT/CONNECT. It just hides the ACCEPT and CONNECT operations and lets the user handle the complexity of identifying the two end points any way he likes. <br>
<br>
I never felt JOIN was needed very badly but it went in as a "what the heck" decision and I do not see that anything has changed.<br>
<br>
Is it because IJOIN seems more difficult than IACCEPT and ICONNECT in some way?<br>
<br>
When you say CANCEL should be deprecated, do you mean MPI_Cancel of an outstanding ISEND/IRECV request or something else?<br>
<br>
Dick Treumann - MPI Team <br>
IBM Systems & Technology Group<br>
Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601<br>
Tele (845) 433-7846 Fax (845) 433-8363<br>
<br>
<br>
<img width="16" height="16" src="cid:1__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt="Inactive hide details for "Supalov, Alexander" ---01/13/2010 02:53:18 PM---Thanks. I meant the JOIN per se as a way of establis"><font color="#424282">"Supalov, Alexander" ---01/13/2010 02:53:18 PM---Thanks. I meant the JOIN per se as a way of establishing the communicator. Do we need that still? Wh</font><br>
<br>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="1%"><img width="96" height="1" src="cid:2__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2" color="#5F5F5F">From:</font></td><td width="100%"><img width="1" height="1" src="cid:2__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">"Supalov, Alexander" <alexander.supalov@intel.com></font></td></tr>
<tr valign="top"><td width="1%"><img width="96" height="1" src="cid:2__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2" color="#5F5F5F">To:</font></td><td width="100%"><img width="1" height="1" src="cid:2__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">"MPI 3.0 Fault Tolerance and Dynamic Process Control working Group" <mpi3-ft@lists.mpi-forum.org></font></td></tr>
<tr valign="top"><td width="1%"><img width="96" height="1" src="cid:2__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2" color="#5F5F5F">Date:</font></td><td width="100%"><img width="1" height="1" src="cid:2__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">01/13/2010 02:53 PM</font></td></tr>
<tr valign="top"><td width="1%"><img width="96" height="1" src="cid:2__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2" color="#5F5F5F">Subject:</font></td><td width="100%"><img width="1" height="1" src="cid:2__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">Re: [Mpi3-ft] Nonblocking Process Creation and Management</font></td></tr>
<tr valign="top"><td width="1%"><img width="96" height="1" src="cid:2__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2" color="#5F5F5F">Sent by:</font></td><td width="100%"><img width="1" height="1" src="cid:2__=0ABBFC39DFE3960E8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">mpi3-ft-bounces@lists.mpi-forum.org</font></td></tr>
</table>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<tt>Thanks. I meant the JOIN per se as a way of establishing the communicator. Do we need that still? What practically relevant cases can be provided to justify its continuing existence? If there are none, we should rather deprecate the JOIN and drop the IJOIN.<br>
<br>
Good point on the CANCEL.<br>
<br>
-----Original Message-----<br>
From: mpi3-ft-bounces@lists.mpi-forum.org [</tt><tt><a href="mailto:mpi3-ft-bounces@lists.mpi-forum.org">mailto:mpi3-ft-bounces@lists.mpi-forum.org</a></tt><tt>] On Behalf Of Josh Hursey<br>
Sent: Wednesday, January 13, 2010 8:25 PM<br>
To: MPI 3.0 Fault Tolerance and Dynamic Process Control working Group<br>
Subject: Re: [Mpi3-ft] Nonblocking Process Creation and Management<br>
<br>
Since join() does a handshake to create the new communicator, it <br>
should be delayed by the remote side of the protocol. A nonblocking <br>
version would allow the application to possibly do other computation <br>
while waiting for the remote side.<br>
<br>
As far as Cancel, I have been thinking that it might be useful for <br>
Accept and Connect. Though with the normal problems of Cancel, I don't <br>
know how to really specify it. I want to look into it a bit more <br>
before next week to see if anything useful can be said of using Cancel <br>
with Accept/Connect.<br>
<br>
-- Josh<br>
<br>
On Jan 13, 2010, at 2:01 PM, Supalov, Alexander wrote:<br>
<br>
> Hi,<br>
><br>
> Do we really need the IJOIN thing? I think the JOIN itself should be <br>
> deprecated. Just as CANCEL, by the way.<br>
><br>
> Best regards.<br>
><br>
> Alexander<br>
><br>
> -----Original Message-----<br>
> From: mpi3-ft-bounces@lists.mpi-forum.org [</tt><tt><a href="mailto:mpi3-ft-bounces@lists.mpi-forum.org">mailto:mpi3-ft-bounces@lists.mpi-forum.org</a></tt><tt> <br>
> ] On Behalf Of Josh Hursey<br>
> Sent: Tuesday, January 12, 2010 11:04 PM<br>
> To: MPI 3.0 Fault Tolerance and Dynamic Process Control working Group<br>
> Subject: [Mpi3-ft] Nonblocking Process Creation and Management<br>
><br>
> I extended and cleaned up the Nonblocking Process Creation and<br>
> Management proposal on the wiki:<br>
> </tt><tt><a href="https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/Async-proc-mgmt">https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/Async-proc-mgmt</a></tt><tt><br>
><br>
> I added the rest of the nonblocking interface proposals, and touched<br>
> up some of the language. I do not have an implementation yet, but will<br>
> work on that next. There are a few items that I need to refine a bit<br>
> still (e.g., MPI_Cancel, mixing of blocking and nonblocking), but this<br>
> should give us a foundation to start from.<br>
><br>
> I would like to talk about this next week during our working group<br>
> slot at the MPI Forum meeting.<br>
><br>
> Let me know what you think, and if you see any problems.<br>
><br>
> Thanks,<br>
> Josh<br>
><br>
> _______________________________________________<br>
> mpi3-ft mailing list<br>
> mpi3-ft@lists.mpi-forum.org<br>
> </tt><tt><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft</a></tt><tt><br>
> ---------------------------------------------------------------------<br>
> Intel GmbH<br>
> Dornacher Strasse 1<br>
> 85622 Feldkirchen/Muenchen Germany<br>
> Sitz der Gesellschaft: Feldkirchen bei Muenchen<br>
> Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer<br>
> Registergericht: Muenchen HRB 47456 Ust.-IdNr.<br>
> VAT Registration No.: DE129385895<br>
> Citibank Frankfurt (BLZ 502 109 00) 600119052<br>
><br>
> This e-mail and any attachments may contain confidential material for<br>
> the sole use of the intended recipient(s). Any review or distribution<br>
> by others is strictly prohibited. If you are not the intended<br>
> recipient, please contact the sender and delete all copies.<br>
><br>
><br>
> _______________________________________________<br>
> mpi3-ft mailing list<br>
> mpi3-ft@lists.mpi-forum.org<br>
> </tt><tt><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft</a></tt><tt><br>
<br>
_______________________________________________<br>
mpi3-ft mailing list<br>
mpi3-ft@lists.mpi-forum.org<br>
</tt><tt><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft</a></tt><tt><br>
---------------------------------------------------------------------<br>
Intel GmbH<br>
Dornacher Strasse 1<br>
85622 Feldkirchen/Muenchen Germany<br>
Sitz der Gesellschaft: Feldkirchen bei Muenchen<br>
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer<br>
Registergericht: Muenchen HRB 47456 Ust.-IdNr.<br>
VAT Registration No.: DE129385895<br>
Citibank Frankfurt (BLZ 502 109 00) 600119052<br>
<br>
This e-mail and any attachments may contain confidential material for<br>
the sole use of the intended recipient(s). Any review or distribution<br>
by others is strictly prohibited. If you are not the intended<br>
recipient, please contact the sender and delete all copies.<br>
<br>
<br>
_______________________________________________<br>
mpi3-ft mailing list<br>
mpi3-ft@lists.mpi-forum.org<br>
</tt><tt><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft</a></tt><tt><br>
</tt><br>
<br>
</body></html>