[Mpi3-hybridpm] slightly improved document is posted

[Rajeev Thakur]

The issue of whether the new communicator is called COMM_EWORLD or
COMM_WORLD has probably been debated in the working group phone calls,
but I think large applications would want to incrementally add hybrid
features to their code, and for them it would be cleaner to have a
separate COMM_EWORLD that affects only the part of the code they are
messing with. The rest of the code that already makes explicit
references to COMM_WORLD remains unchanged. If we were designing MPI
from scratch, however, it would make sense to include all endpoints in
COMM_WORLD. 

Rajeev
 

> -----Original Message-----
> From: mpi3-hybridpm-bounces at lists.mpi-forum.org 
> [mailto:mpi3-hybridpm-bounces at lists.mpi-forum.org] On Behalf 
> Of Snir, Marc
> Sent: Sunday, January 17, 2010 9:03 PM
> To: mpi3-hybridpm at lists.mpi-forum.org
> Subject: [Mpi3-hybridpm] slightly improved document is posted
> 
> hybrid-V5.2.pdf<https://svn.mpi-forum.org/trac/mpi-forum-web/a
ttachment/wiki/MPI3Hybrid/hybrid-V5.2.pdf>
> 
> Please use this one for our discussion coming week.
> 
> Marc Snir
> 
> 
> 
> 
> 
> _______________________________________________
> Mpi3-hybridpm mailing list
> Mpi3-hybridpm at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-hybridpm
>