<html>
<body>
<blockquote type=cite class=cite cite=""><font face="Verdana">Just to
follow up, I think that the “right” thing to do with respect to some sort
of<br>
transactional model is to have some sort of standard way to request
such <br>
communications take place – probably at init time. We have
had such an MPI<br>
implementation running in production for several years on a
multi-thousand<br>
process cluster, and the only thing that needs to be exposed to the
users is the<br>
ability to turn on/off the functionality – all the rest is
taken care of just fine within<br>
the context of the MPI 2.0 standard, and is 100% standard
compliant.<br>
</font></blockquote>Cool! Can you post the API for this thing? Might be a
useful thing to start from. Also, its a prototype
implementation.<br><br>
<blockquote type=cite class=cite cite=""><font face="Verdana">This does
not deal with hints on the network “state”.<br>
</font></blockquote>Yeah, I'm not sure if such hints are valuable enough
to be included in the spec. It really falls under the quality-of-service
ideas what we've tossed around, so we should write up a proposal for
those and see how much QoS people really want.<br>
<x-sigsep><p></x-sigsep>
Greg Bronevetsky<br>
Post-Doctoral Researcher<br>
1028 Building 451<br>
Lawrence Livermore National Lab<br>
(925) 424-5756<br>
bronevetsky1@llnl.gov</body>
</html>