<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 3, 2018 at 2:12 PM, Rob Falgout hypre Tracker <span dir="ltr"><<a href="mailto:hypre-support@llnl.gov" target="_blank">hypre-support@llnl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
Rob Falgout <<a href="mailto:rfalgout@llnl.gov">rfalgout@llnl.gov</a>> added the comment:<br>
<br>
Hi Barry,<br>
<br>
</span>Can you explain the scenario where multiple hypre solves would be working in parallel with the same communicator?  Thanks!<br></blockquote><div><br></div><div>Hi Rob,<br></div><div><br></div><div>For instance, if an application has multiple fields and each field will be solved by a HYPRE solver,  then we end up with  multiple hypre solves. The  multiple hypre solves are not run simultaneously, instead, it will be run one-by-one. If we assign the same communicator to the  multiple hypre solves, any potential tag conflict?  <br><br></div><div>Fande,<br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-Rob<br>
<span class="gmail-"><br>
______________________________<wbr>______________<br>
hypre Issue Tracker <<a href="mailto:hypre-support@llnl.gov">hypre-support@llnl.gov</a>><br>
</span><<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__cascb1.llnl.gov_hypre_issue1595&d=DwIFaQ&c=54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00&r=DUUt3SRGI0_JgtNaS3udV68GRkgV4ts7XKfj2opmiCY&m=3KsQjTxI8eRWrSIJtB3o9NlBc4bEuuP4HxiT-BlMx3U&s=FjvfvXD21bX8LA2TAD-J6MWCJyMNm0aameRp_9nfLYs&e=" rel="noreferrer" target="_blank">https://urldefense.<wbr>proofpoint.com/v2/url?u=http-<wbr>3A__cascb1.llnl.gov_hypre_<wbr>issue1595&d=DwIFaQ&c=<wbr>54IZrppPQZKX9mLzcGdPfFD1hxrcB_<wbr>_aEkJFOKJFd00&r=DUUt3SRGI0_<wbr>JgtNaS3udV68GRkgV4ts7XKfj2opmi<wbr>CY&m=<wbr>3KsQjTxI8eRWrSIJtB3o9NlBc4bEuu<wbr>P4HxiT-BlMx3U&s=<wbr>FjvfvXD21bX8LA2TAD-<wbr>J6MWCJyMNm0aameRp_9nfLYs&e=</a>><br>
______________________________<wbr>______________<br>
</blockquote></div><br></div></div>