<div dir="ltr"><div>hi Matthew, Jed</div><div> </div><div>Thank you very much for the answer and advise.</div><div> </div><div>Cong</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 16, 2013 at 10:18 PM, Jed Brown <span dir="ltr"><<a href="mailto:jedbrown@mcs.anl.gov" target="_blank">jedbrown@mcs.anl.gov</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">Matthew Knepley <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>> writes:<br>
> Never put in a barrier.<br>
<br>
</div>Barriers serve no functional or correctness purpose in a<br>
properly-written pure-MPI code. They are sometimes useful for debugging<br>
and sometimes necessary if you use despicable hacks like communicating<br>
through a side channel such as the file system. If you're not putting<br>
yourself into that unenviable position, don't use barriers.<br>
</blockquote></div><br></div>