[mpiwg-rma] MPI RMA status summary

Jim Dinan james.dinan at gmail.com
Thu Nov 13 09:38:39 CST 2014


Hi Bill,

#363 - Closed as withdrawn
#366 - Closed as withdrawn

#401 - It would be nice to add this as errata in MPI 3.1, if the WG can
reach agreement on text in time
#439 - Queued up for WG discussion as an MPI 4.0 proposal.  Torsten has a
competing proposal that does not have a ticket registered in Trac.  I added
a link to his slides on #439.

#460 - Not on your list.  This is a proposal for a new info key that was
suggested by a user.  Should be queued up for WG discussion.

 ~Jim.


On Thu, Sep 25, 2014 at 10:19 AM, William Gropp <wgropp at illinois.edu> wrote:

> I looked through all of the tickets and wrote a summary of the open
> issues, which I’ve attached.  I propose the following:
>
> Determine which of these issues can be resolved by email.  A significant
> number can probably be closed with no further action.
>
> For those requiring rework, determine if there is still interest in them,
> and if not, close them as well.
>
> For the ones requiring discussion, assign someone to organize a position
> and discussion.  We can schedule telecons to go over those issues.  The
> first item in the list is certainly in this class.
>
> Comments?
>
> Bill
>
> _______________________________________________
> mpiwg-rma mailing list
> mpiwg-rma at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-rma
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-rma/attachments/20141113/6ba429ce/attachment.html>


More information about the mpiwg-rma mailing list