<html><body>
<p>Greg - <br>
<br>
you are correct and I am a bit embarassed by my word choice. To "insure" can mean "to join with others to distribute or smooth risk". To "ensure" is to "make certain it will be so".<br>
<br>
Thanks<br>
<br>
Dick Treumann - MPI Team/TCEM <br>
IBM Systems & Technology Group<br>
Dept 0lva / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601<br>
Tele (845) 433-7846 Fax (845) 433-8363<br>
<br>
<br>
<tt>mpi-21-bounces@cs.uiuc.edu wrote on 01/31/2008 05:56:55 PM:<br>
<br>
> On Thu, Jan 31, 2008 at 09:26:07PM +0100, Rolf Rabenseifner wrote:<br>
> <br>
> > Dick, I fully agree. I withdraw my proposals with OpenMP and come <br>
> > back to your text, adding the forward reference to MPI_IS_THREAD_MAIN:<br>
> > <br>
> > >> >>> MPI_THREAD_FUNNELED The process may be multi-threaded, but the<br>
> > >> >>> application<br>
> > >> >>> must insure that only the main thread makes MPI calls<br>
> > (for the definition of main thread, see MPI_IS_THREAD_MAIN).<br>
> > <br>
> > By the way, this clarification is independent of any <br>
> > additional level of thread support taht may be specified in<br>
> > further MPI versions. <br>
> <br>
> I also agree with this version of the clarification.<br>
> <br>
> BTW, it should be "ensure", not "insure". The current MPI 2.0 doc has<br>
> "ensure" 28 times and "insure" 0 times.<br>
> <br>
> -- greg<br>
> <br>
> _______________________________________________<br>
> mpi-21 mailing list<br>
> mpi-21@cs.uiuc.edu<br>
> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/mpi-21">http://lists.cs.uiuc.edu/mailman/listinfo/mpi-21</a><br>
</tt></body></html>