[Mpi3-rma] [EXTERNAL] RMA WG discussion

[Barrett, Brian W]

Also, this morning we had a fairly good meeting with the FT group.  The
outcome of the discussion was that it would seem like a good path forward
would be for the RMA working group to define what we can and can not
provide in terms of failure reporting and state stability after a
fail-stop failure of a process.  I offered to write up a starting
document, which I hope to have circulated inside the RMA WG by January, so
that we can make progress at the March meeting.

Brian

On 12/5/12 2:14 PM, "Pavan Balaji" <balaji at mcs.anl.gov> wrote:

>
>We talked about different items that need to be addressed for (1) MPI-3
>Errata (should only be bug fixes, not all small changes), and (2) MPI-3.1.
>
>We still need to discuss the below items in a telecon; this is just a
>basic separation we did based on the WG discussion.
>
>MPI-3 Errata
>============
>1. Ticket #348 -- one of the examples has a bug in it, which should be
>fixed.
>
>2. Ticket #350 -- we should state that for MPI_ACCUMULATE with
>MPI_NO_OP, the MPI implementation is not allowed to throw an error when
>the origin buffer is NULL.
>
>MPI-3.1
>=======
>1. Ticket #344 -- Shared memory attribute query.
>
>2. Ticket #346 -- Info keys are not consistent across window creation
>routines.
>
>3. Ticket #347 -- Info keys are not listed in the appendix.
>
>4. Ticket #349 -- Addition of MPI_Disp_to_aint and MPI_Aint_to_disp.
>
>5. Addition of the MPI_MODE_NOLOAD assertion.  RMA slides have info on
>this.
>
>6. Info argument addition for req_mem_model.  RMA slides have info on
>this.
>
> -- Pavan
>
>-- 
>Pavan Balaji
>http://www.mcs.anl.gov/~balaji
>_______________________________________________
>mpi3-rma mailing list
>mpi3-rma at lists.mpi-forum.org
>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma
>
>


--
  Brian W. Barrett
  Scalable System Software Group
  Sandia National Laboratories