<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think the statement explains it - during the MPI 2 discussions, there was a lot of effort spent on defining a portable, standard, resource control specification. The forum was unable to reach a consensus, and rather than make a poor specification, they left it undefined. This permits MPI implementations to explore interfaces with their resource management systems (and permits an MPI-based cluster to be reconfigurable), just not in a MPI-standard defined way. Note that the info argument to the spawn routines, for example, provides a way to communicate with a resource manager; it was an explicit goal of the design of info to provide this way to communication information that is outside of the specification.<div><br></div><div>Bill</div><div><br><div><div>On Jun 30, 2010, at 2:56 PM, siavash ghiasvand wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><font face="tahoma,sans-serif">Hi,</font></div><div><font face="tahoma,sans-serif"> </font></div><div><font face="tahoma,sans-serif">In MPI22 Standard document [</font><font face="tahoma,sans-serif"><a href="http://www.mpi-forum.org/docs/mpi-2.2/mpi22-report.pdf" target="_blank"><b><font color="#3333ff">1</font></b></a></font><font face="tahoma,sans-serif">] on page 305 lines 27-30 we can see this paragraph:</font></div> <div><font face="tahoma,sans-serif"> </font></div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="tahoma,sans-serif"><font color="#666666">The MPI Forum decided not to address resource control because it was not able to</font><font color="#666666"><br> </font></font></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="tahoma,sans-serif"><font color="#666666">design a portable interface that would be appropriate for the broad spectrum of existing</font><font color="#666666"><br> </font></font></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="tahoma,sans-serif"><font color="#666666">and potential resource and process controllers. Resource control can encompass a wide</font><font color="#666666"><br> </font></font></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="tahoma,sans-serif"><font color="#666666">range of abilities, including adding and deleting nodes from a virtual parallel machine, ...</font></font><font face="tahoma,sans-serif"><br> </font></blockquote><font face="tahoma,sans-serif"> <br></font></div><div><font face="tahoma,sans-serif">Which means, an MPI-based cluster is not reconfigurable at run time! but in EuroPVM/MPI 2006 a reconfigurable version of MPI for HPC clusters was described by University of New Mexico Scalable Systems Lab [</font><font face="tahoma,sans-serif"><a href="http://www.pvmmpi06.org/talks/CommProt/venkata.pdf" target="_blank"><b><font color="#3333ff">2</font></b></a></font><font face="tahoma,sans-serif">] and they show that their implementation will enhance performance (the main goal of MPI). So, why in MPI22 standard "<i>The MPI forum decided not to address resource control</i>" which can improve both flexibility and performance of an MPI-based cluster?</font></div> <div><font face="tahoma,sans-serif"> </font></div><div><font face="tahoma,sans-serif"> </font></div><div><font face="tahoma,sans-serif">Ref:</font></div><div><font face="tahoma,sans-serif"><a href="http://www.springerlink.com/content/w588601267363238/">MPI/CTP: A Reconfigurable MPI for HPC Applications</a></font></div> <div><font face="tahoma,sans-serif"> </font></div><div><font face="tahoma,sans-serif"> <br clear="all"></font></div>Regards,<br>Siavash<br> </div> <span><ATT00001..txt></span></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>William Gropp</div><div>Deputy Director for Research</div><div>Institute for Advanced Computing Applications and Technologies</div><div>Paul and Cynthia Saylor Professor of Computer Science</div><div>University of Illinois Urbana-Champaign</div><div><br class="khtml-block-placeholder"></div></div><br class="Apple-interchange-newline"></span></div></span><br class="Apple-interchange-newline"> </div><br></div></body></html>