<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 27, 2012, at 6:58 PM, Jed Brown wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Fri, Jan 27, 2012 at 17:48, Matthew Knepley <span dir="ltr"><<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Is now the right time. Shouldn't we wait until MPI's replacement is working and do things with that model?</blockquote>
<div><br></div></div><div>I'm laughing. Am I supposed to be?</div></blockquote></div><br><div>I'm laughing too.<br><br>There isn't going to be a replacement for MPI until the smart people that understand parallel programming, performance, and libraries start working on something other than MPI. But most of those people are on the MPI Forum, trying to improve MPI. Now we need a good model for threads, and that might not be based on MPI, but it sure looks like the large-scale distributed-memory model will be MPI for the foreseeable future.</div>
<div><br></div></blockquote><div><br></div><div>I don't think its a matter of smart people not having worked on this, they have IMO, its just a hard problem.</div><br><blockquote type="cite"><div><br></div><div>As for sources of parallel errors, yes, it's somewhat tricky, but as long as the model is to get a sub-object out of a bigger one (submatrix, coarse level, etc), I think we can manage it. At any particular time, the user should still be looking at essentially single-comm collections of objects, but not all processes will end up being called in every context.</div>
</blockquote></div><br></body></html>