[Mpi-22] reConfigurable MPI

[Solt, David George]

Hi Siavash,

A couple of reasons for this statement:


1)       The 2.2 standard was an update to the 2.0 standard which predates the 2006 paper you referenced.  2.2 only introduced new functions where there was an urgent need.   New features are intended for the forthcoming 3.0.

2)       The resource control paragraph is in the context of process creation and my quick 1 minute scan of the paper you referenced indicates that it is discussing reconfiguring communication and does not talk about dynamic processes.

Thanks,
Dave Solt

From: mpi-22-bounces_at_[hidden] [mailto:mpi-22-bounces_at_[hidden]] On Behalf Of siavash ghiasvand
Sent: Wednesday, June 30, 2010 2:57 PM
To: mpi-22_at_[hidden]
Subject: [Mpi-22] reConfigurable MPI

Hi,

In MPI22 Standard document [1<http://www.mpi-forum.org/docs/mpi-2.2/mpi22-report.pdf>] on page 305 lines 27-30 we can see this paragraph:

The MPI Forum decided not to address resource control because it was not able to
design a portable interface that would be appropriate for the broad spectrum of existing
and potential resource and process controllers. Resource control can encompass a wide
range of abilities, including adding and deleting nodes from a virtual parallel machine, ...

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 [2<http://www.pvmmpi06.org/talks/CommProt/venkata.pdf>] and they show that their implementation will enhance performance (the main goal of MPI). So, why in MPI22 standard "The MPI forum decided not to address resource control" which can improve both flexibility and performance of an MPI-based cluster?


Ref:
MPI/CTP: A Reconfigurable MPI for HPC Applications<http://www.springerlink.com/content/w588601267363238/>


Regards,
Siavash


* 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpi-22/attachments/20100630/24f65e27/attachment.html>