- mpiwg-rma - mailman3.cels.anl.gov

RMA WG recurring telecon
by Thakur, Rajeev 24 Sep '18

24 Sep '18

Today’s telecon is canceled since the group just met on Friday at the Forum. Rajeev

1 0

Re: [mpiwg-rma] Summary of MPI RMA WG meeting on Sept 21, 2018
by William Gropp 23 Sep '18

23 Sep '18

In general, what I’d like to do is resurrect the wiki, as that was a good way to manage broader discussions, though the less friendly venue of an issue could be used. For this one, we have some research results, at least one presentation of the concepts for MPI, and some concerns; I’d like to gather these in one place and then work on addressing the concerns. Bill William Gropp Director and Chief Scientist, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign > On Sep 23, 2018, at 7:20 AM, Tony Skjellum <skjellum(a)gmail.com> wrote: > > Bill et al, I held back on the non-blocking APIs for RMA non-blocking collectives ... happy to discuss how we jointly get from here to there ... I think Pavan raised some concerns and we put on hold... happy to write ticket ... now that I am subscribed to group, can cross correlate with collective WG... please advise on preferred approach to advancing ... > Thx > Tony > > Anthony Skjellum, PhD > 205-807-4968 > > > On Sep 21, 2018, at 3:55 PM, William Gropp via mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org <mailto:[email protected]>> wrote: > >> An amendment - the Shared-query has a full proposal, see https://github.com/mpiwg-rma/mpi-standard/commit/fcfa116935376d65f3bb28332d… <https://github.com/mpiwg-rma/mpi-standard/commit/fcfa116935376d65f3bb28332d…> . We need volunteers to read it carefully and review it. >> >> Bill >> >> William Gropp >> Director and Chief Scientist, NCSA >> Thomas M. Siebel Chair in Computer Science >> University of Illinois Urbana-Champaign >> >> >> >> >> >> >>> On Sep 21, 2018, at 8:52 AM, William Gropp via mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org <mailto:[email protected]>> wrote: >>> >>> MPI RMA Working Group Meeting >>> September 21, 2018 >>> Barcelona, Spain >>> >>> (I couldn’t find the RMA wiki - did this never get migrated?) >>> >>> Here are my notes. For those present, please let me know if I missed anything. >>> >>> - Interoperability of MPI shared memory with C11, C++11 language semantics. Lead: Bill Gropp >>> >>> No document. >>> >>> Discussion. WG agreed that MPI should remain as consistent as possible with the language standards as they go forward, noting that there are still limitations in their descriptions of shared memory. >>> >>> - MPI Generalized atomics. Lead: Pavan Balaji >>> >>> PDF attached. >>> >>> Generally positive response to the text. A few suggestions were made: >>> For accumulate_op - allow compare-and-swap (CAS) with another op (as an option) >>> For which_accumulate_op - Consider a comma-separated list of operators >>> for accumulate_max_bytes. There was a discussion about whether this should be count or bytes, and how exactly to describe what the max means in terms of parameters to the accumulate operations. >>> >>> - Neighborhood communication in RMA. Lead: Nathan Hjelm >>> >>> No document. >>> >>> Nathan presented the basic ideas, which is the use of the topology attached to a communicator to limit the permitted communication partners, and thus simplify and reduce the memory requirements in the implementation. >>> >>> The WG was interested, and on a straw vote of 6-0-2, asked for a more detailed presentation (e.g., a Powerpoint, not yet a written standard proposal), >>> >>> - Nonblocking RMA synchronization. Lead: Pavan Balaji >>> >>> No document, but this might be absorbed by TonyS's proposal. >>> >>> The WG would like a top-level conceptual discussion of this in the context of MPI. >>> >>> - RMA Notify. Leads: Jim and Torsten >>> >>> https://github.com/mpi-forum/mpi-issues/issues/59 <https://github.com/mpi-forum/mpi-issues/issues/59> >>> >>> Some discussion. Noted that the state-of-the-art has advanced since the last discussion in detail by the working group. The WG, on a 7-0-1 straw vote, would like an update to the possible options here. It was also noted that Bull is experimenting with different options in different systems, and may be able to share the results in a few months. >>> >>> One question to consider is the pros and cons of using requests as the notification mechanism; it was noted that one pragmatic if not elegant solution might be to allow both a heavy (e.g., MPI_Request) and lightweight (e.g., memory variable) notification approach. >>> >>> - MPI_IN_PLACE semantics for collectives on shared memory. Lead: Pavan Balaji >>> >>> PDF attached. >>> >>> This was reviewed by the WG. When asked whether there was interest in a document with a usage example and discussion of benefits, the WG voted no in a straw poll with 0-4-2 (and 2 not voting). >>> >>> - Relax constraints on MPI_WIN_SHARED_QUERY. Lead: Jeff Hammond >>> >>> https://github.com/mpi-forum/mpi-issues/issues/23 <https://github.com/mpi-forum/mpi-issues/issues/23> >>> >>> The WG found support for this and voted 5-1-2 for a full written proposal >>> >>> - Add flush_thread synchronization calls. Lead: Nathan Hjelm >>> >>> No document. >>> >>> Nathan presented this and the WG voted 7-0-2 for a more detailed (e.g., a Powerpoint) description. >>> >>> The WG would like to see the written proposals for generalized atomics and shared_query in time for reading at the December MPI Forum meeting. >>> >>> >>> The WG adjourned after discussing these items. >>> >>> William Gropp >>> Director and Chief Scientist, NCSA >>> Thomas M. Siebel Chair in Computer Science >>> University of Illinois Urbana-Champaign >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> mpiwg-rma mailing list >>> mpiwg-rma(a)lists.mpi-forum.org <mailto:[email protected]> >>> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma <https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma> >> >> _______________________________________________ >> mpiwg-rma mailing list >> mpiwg-rma(a)lists.mpi-forum.org <mailto:[email protected]> >> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma <https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma>

1 0

Re: [mpiwg-rma] Summary of MPI RMA WG meeting on Sept 21, 2018
by Tony Skjellum 23 Sep '18

23 Sep '18

Bill et al, I held back on the non-blocking APIs for RMA non-blocking collectives ... happy to discuss how we jointly get from here to there ... I think Pavan raised some concerns and we put on hold... happy to write ticket ... now that I am subscribed to group, can cross correlate with collective WG... please advise on preferred approach to advancing ... Thx Tony Anthony Skjellum, PhD 205-807-4968 > On Sep 21, 2018, at 3:55 PM, William Gropp via mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org> wrote: > > An amendment - the Shared-query has a full proposal, see https://github.com/mpiwg-rma/mpi-standard/commit/fcfa116935376d65f3bb28332d… . We need volunteers to read it carefully and review it. > > Bill > > William Gropp > Director and Chief Scientist, NCSA > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > > > > > > >> On Sep 21, 2018, at 8:52 AM, William Gropp via mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org> wrote: >> >> MPI RMA Working Group Meeting >> September 21, 2018 >> Barcelona, Spain >> >> (I couldn’t find the RMA wiki - did this never get migrated?) >> >> Here are my notes. For those present, please let me know if I missed anything. >> >> - Interoperability of MPI shared memory with C11, C++11 language semantics. Lead: Bill Gropp >> >> No document. >> >> Discussion. WG agreed that MPI should remain as consistent as possible with the language standards as they go forward, noting that there are still limitations in their descriptions of shared memory. >> >> - MPI Generalized atomics. Lead: Pavan Balaji >> >> PDF attached. >> >> Generally positive response to the text. A few suggestions were made: >> For accumulate_op - allow compare-and-swap (CAS) with another op (as an option) >> For which_accumulate_op - Consider a comma-separated list of operators >> for accumulate_max_bytes. There was a discussion about whether this should be count or bytes, and how exactly to describe what the max means in terms of parameters to the accumulate operations. >> >> - Neighborhood communication in RMA. Lead: Nathan Hjelm >> >> No document. >> >> Nathan presented the basic ideas, which is the use of the topology attached to a communicator to limit the permitted communication partners, and thus simplify and reduce the memory requirements in the implementation. >> >> The WG was interested, and on a straw vote of 6-0-2, asked for a more detailed presentation (e.g., a Powerpoint, not yet a written standard proposal), >> >> - Nonblocking RMA synchronization. Lead: Pavan Balaji >> >> No document, but this might be absorbed by TonyS's proposal. >> >> The WG would like a top-level conceptual discussion of this in the context of MPI. >> >> - RMA Notify. Leads: Jim and Torsten >> >> https://github.com/mpi-forum/mpi-issues/issues/59 >> >> Some discussion. Noted that the state-of-the-art has advanced since the last discussion in detail by the working group. The WG, on a 7-0-1 straw vote, would like an update to the possible options here. It was also noted that Bull is experimenting with different options in different systems, and may be able to share the results in a few months. >> >> One question to consider is the pros and cons of using requests as the notification mechanism; it was noted that one pragmatic if not elegant solution might be to allow both a heavy (e.g., MPI_Request) and lightweight (e.g., memory variable) notification approach. >> >> - MPI_IN_PLACE semantics for collectives on shared memory. Lead: Pavan Balaji >> >> PDF attached. >> >> This was reviewed by the WG. When asked whether there was interest in a document with a usage example and discussion of benefits, the WG voted no in a straw poll with 0-4-2 (and 2 not voting). >> >> - Relax constraints on MPI_WIN_SHARED_QUERY. Lead: Jeff Hammond >> >> https://github.com/mpi-forum/mpi-issues/issues/23 >> >> The WG found support for this and voted 5-1-2 for a full written proposal >> >> - Add flush_thread synchronization calls. Lead: Nathan Hjelm >> >> No document. >> >> Nathan presented this and the WG voted 7-0-2 for a more detailed (e.g., a Powerpoint) description. >> >> The WG would like to see the written proposals for generalized atomics and shared_query in time for reading at the December MPI Forum meeting. >> >> >> The WG adjourned after discussing these items. >> >> William Gropp >> Director and Chief Scientist, NCSA >> Thomas M. Siebel Chair in Computer Science >> University of Illinois Urbana-Champaign >> >> >> >> >> >> >> _______________________________________________ >> mpiwg-rma mailing list >> mpiwg-rma(a)lists.mpi-forum.org >> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma > > _______________________________________________ > mpiwg-rma mailing list > mpiwg-rma(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma

1 0

Bugs in RMA in current MPI standard - Re: Summary of MPI RMA WG meeting on Sept 21, 2018
by Rolf Rabenseifner 23 Sep '18

23 Sep '18

Dear Bill, 1. MPI-3.1 after MPI_Win_UNLOCK_ALL, page 448 lines 1-4 read Implementors may restrict the use of RMA communication that is synchronized by lock calls to windows in memory allocated by MPI_ALLOC_MEM (Section 8.2), MPI_WIN_ALLOCATE (Section 11.2.2), or attached with MPI_WIN_ATTACH (Section 11.2.4). Locks can be used portably only in such memory. but should read Implementors may restrict the use of RMA communication that is synchronized by lock calls to windows in memory allocated by MPI_ALLOC_MEM (Section 8.2), MPI_WIN_ALLOCATE (Section 11.2.2), MPI_WIN_ALLOCATE_SHARED (Section 11.2.3), or attached with MPI_WIN_ATTACH (Section 11.2.4). Locks can be used portably only in such memory. 2. In MPI-3.1 Section 11.5.5 Assertions, the wording of data transfer assertions does not fit to shared memory windows. I exxpect the fact is clear because the window portions of process rank a can be written or read by all process unsing direct language assignments or expressions, resprectively, instead of only using RMA calls and direct accesses only to the own window Portion. Therefore, I would add at the end of the following items - MPI_WIN_POST: MPI_MODE_NOSTORE and MPI_MODE_NOPUT - MPI_WIN_FENCE: at all four assertions the following sentence: This assertion does not apply and is therefore ignored in the case of a window created with MPI_WIN_ALLOCATE_SHARED. Best regards Rolf ----- Original Message ----- > From: "MPI WG Remote Memory Access working group" <mpiwg-rma(a)lists.mpi-forum.org> > To: "MPI WG Remote Memory Access working group" <mpiwg-rma(a)lists.mpi-forum.org> > Cc: "wgropp" <wgropp(a)illinois.edu> > Sent: Friday, September 21, 2018 3:52:07 PM > Subject: [mpiwg-rma] Summary of MPI RMA WG meeting on Sept 21, 2018 > MPI RMA Working Group Meeting > September 21, 2018 > Barcelona, Spain > > (I couldn’t find the RMA wiki - did this never get migrated?) > > Here are my notes. For those present, please let me know if I missed anything. > > - Interoperability of MPI shared memory with C11, C++11 language semantics. > Lead: Bill Gropp > > No document. > > Discussion. WG agreed that MPI should remain as consistent as possible with the > language standards as they go forward, noting that there are still limitations > in their descriptions of shared memory. > > - MPI Generalized atomics. Lead: Pavan Balaji > > PDF attached. > > Generally positive response to the text. A few suggestions were made: > For accumulate_op - allow compare-and-swap (CAS) with another op (as an option) > For which_accumulate_op - Consider a comma-separated list of operators > for accumulate_max_bytes. There was a discussion about whether this should be > count or bytes, and how exactly to describe what the max means in terms of > parameters to the accumulate operations. > > - Neighborhood communication in RMA. Lead: Nathan Hjelm > > No document. > > Nathan presented the basic ideas, which is the use of the topology attached to a > communicator to limit the permitted communication partners, and thus simplify > and reduce the memory requirements in the implementation. > > The WG was interested, and on a straw vote of 6-0-2, asked for a more detailed > presentation (e.g., a Powerpoint, not yet a written standard proposal), > > - Nonblocking RMA synchronization. Lead: Pavan Balaji > > No document, but this might be absorbed by TonyS's proposal. > > The WG would like a top-level conceptual discussion of this in the context of > MPI. > > - RMA Notify. Leads: Jim and Torsten > > [ https://github.com/mpi-forum/mpi-issues/issues/59 | > https://github.com/mpi-forum/mpi-issues/issues/59 ] > > Some discussion. Noted that the state-of-the-art has advanced since the last > discussion in detail by the working group. The WG, on a 7-0-1 straw vote, would > like an update to the possible options here. It was also noted that Bull is > experimenting with different options in different systems, and may be able to > share the results in a few months. > > One question to consider is the pros and cons of using requests as the > notification mechanism; it was noted that one pragmatic if not elegant solution > might be to allow both a heavy (e.g., MPI_Request) and lightweight (e.g., > memory variable) notification approach. > > - MPI_IN_PLACE semantics for collectives on shared memory. Lead: Pavan Balaji > > PDF attached. > > This was reviewed by the WG. When asked whether there was interest in a document > with a usage example and discussion of benefits, the WG voted no in a straw > poll with 0-4-2 (and 2 not voting). > > - Relax constraints on MPI_WIN_SHARED_QUERY. Lead: Jeff Hammond > > [ https://github.com/mpi-forum/mpi-issues/issues/23 | > https://github.com/mpi-forum/mpi-issues/issues/23 ] > > The WG found support for this and voted 5-1-2 for a full written proposal > > - Add flush_thread synchronization calls. Lead: Nathan Hjelm > > No document. > > Nathan presented this and the WG voted 7-0-2 for a more detailed (e.g., a > Powerpoint) description. > > The WG would like to see the written proposals for generalized atomics and > shared_query in time for reading at the December MPI Forum meeting. > > > The WG adjourned after discussing these items. > > William Gropp > Director and Chief Scientist, NCSA > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > > > > > > > > _______________________________________________ > mpiwg-rma mailing list > mpiwg-rma(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 . University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 . Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) .

1 0

Re: [mpiwg-rma] Summary of MPI RMA WG meeting on Sept 21, 2018
by William Gropp 21 Sep '18

21 Sep '18

An amendment - the Shared-query has a full proposal, see https://github.com/mpiwg-rma/mpi-standard/commit/fcfa116935376d65f3bb28332d… . We need volunteers to read it carefully and review it. Bill William Gropp Director and Chief Scientist, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign > On Sep 21, 2018, at 8:52 AM, William Gropp via mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org> wrote: > > MPI RMA Working Group Meeting > September 21, 2018 > Barcelona, Spain > > (I couldn’t find the RMA wiki - did this never get migrated?) > > Here are my notes. For those present, please let me know if I missed anything. > > - Interoperability of MPI shared memory with C11, C++11 language semantics. Lead: Bill Gropp > > No document. > > Discussion. WG agreed that MPI should remain as consistent as possible with the language standards as they go forward, noting that there are still limitations in their descriptions of shared memory. > > - MPI Generalized atomics. Lead: Pavan Balaji > > PDF attached. > > Generally positive response to the text. A few suggestions were made: > For accumulate_op - allow compare-and-swap (CAS) with another op (as an option) > For which_accumulate_op - Consider a comma-separated list of operators > for accumulate_max_bytes. There was a discussion about whether this should be count or bytes, and how exactly to describe what the max means in terms of parameters to the accumulate operations. > > - Neighborhood communication in RMA. Lead: Nathan Hjelm > > No document. > > Nathan presented the basic ideas, which is the use of the topology attached to a communicator to limit the permitted communication partners, and thus simplify and reduce the memory requirements in the implementation. > > The WG was interested, and on a straw vote of 6-0-2, asked for a more detailed presentation (e.g., a Powerpoint, not yet a written standard proposal), > > - Nonblocking RMA synchronization. Lead: Pavan Balaji > > No document, but this might be absorbed by TonyS's proposal. > > The WG would like a top-level conceptual discussion of this in the context of MPI. > > - RMA Notify. Leads: Jim and Torsten > > https://github.com/mpi-forum/mpi-issues/issues/59 <https://github.com/mpi-forum/mpi-issues/issues/59> > > Some discussion. Noted that the state-of-the-art has advanced since the last discussion in detail by the working group. The WG, on a 7-0-1 straw vote, would like an update to the possible options here. It was also noted that Bull is experimenting with different options in different systems, and may be able to share the results in a few months. > > One question to consider is the pros and cons of using requests as the notification mechanism; it was noted that one pragmatic if not elegant solution might be to allow both a heavy (e.g., MPI_Request) and lightweight (e.g., memory variable) notification approach. > > - MPI_IN_PLACE semantics for collectives on shared memory. Lead: Pavan Balaji > > PDF attached. > > This was reviewed by the WG. When asked whether there was interest in a document with a usage example and discussion of benefits, the WG voted no in a straw poll with 0-4-2 (and 2 not voting). > > - Relax constraints on MPI_WIN_SHARED_QUERY. Lead: Jeff Hammond > > https://github.com/mpi-forum/mpi-issues/issues/23 <https://github.com/mpi-forum/mpi-issues/issues/23> > > The WG found support for this and voted 5-1-2 for a full written proposal > > - Add flush_thread synchronization calls. Lead: Nathan Hjelm > > No document. > > Nathan presented this and the WG voted 7-0-2 for a more detailed (e.g., a Powerpoint) description. > > The WG would like to see the written proposals for generalized atomics and shared_query in time for reading at the December MPI Forum meeting. > > > The WG adjourned after discussing these items. > > William Gropp > Director and Chief Scientist, NCSA > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > > > > > > > _______________________________________________ > mpiwg-rma mailing list > mpiwg-rma(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma

1 0

Summary of MPI RMA WG meeting on Sept 21, 2018
by William Gropp 21 Sep '18

21 Sep '18

MPI RMA Working Group Meeting September 21, 2018 Barcelona, Spain (I couldn’t find the RMA wiki - did this never get migrated?) Here are my notes. For those present, please let me know if I missed anything. - Interoperability of MPI shared memory with C11, C++11 language semantics. Lead: Bill Gropp No document. Discussion. WG agreed that MPI should remain as consistent as possible with the language standards as they go forward, noting that there are still limitations in their descriptions of shared memory. - MPI Generalized atomics. Lead: Pavan Balaji PDF attached. Generally positive response to the text. A few suggestions were made: For accumulate_op - allow compare-and-swap (CAS) with another op (as an option) For which_accumulate_op - Consider a comma-separated list of operators for accumulate_max_bytes. There was a discussion about whether this should be count or bytes, and how exactly to describe what the max means in terms of parameters to the accumulate operations. - Neighborhood communication in RMA. Lead: Nathan Hjelm No document. Nathan presented the basic ideas, which is the use of the topology attached to a communicator to limit the permitted communication partners, and thus simplify and reduce the memory requirements in the implementation. The WG was interested, and on a straw vote of 6-0-2, asked for a more detailed presentation (e.g., a Powerpoint, not yet a written standard proposal), - Nonblocking RMA synchronization. Lead: Pavan Balaji No document, but this might be absorbed by TonyS's proposal. The WG would like a top-level conceptual discussion of this in the context of MPI. - RMA Notify. Leads: Jim and Torsten https://github.com/mpi-forum/mpi-issues/issues/59 <https://github.com/mpi-forum/mpi-issues/issues/59> Some discussion. Noted that the state-of-the-art has advanced since the last discussion in detail by the working group. The WG, on a 7-0-1 straw vote, would like an update to the possible options here. It was also noted that Bull is experimenting with different options in different systems, and may be able to share the results in a few months. One question to consider is the pros and cons of using requests as the notification mechanism; it was noted that one pragmatic if not elegant solution might be to allow both a heavy (e.g., MPI_Request) and lightweight (e.g., memory variable) notification approach. - MPI_IN_PLACE semantics for collectives on shared memory. Lead: Pavan Balaji PDF attached. This was reviewed by the WG. When asked whether there was interest in a document with a usage example and discussion of benefits, the WG voted no in a straw poll with 0-4-2 (and 2 not voting). - Relax constraints on MPI_WIN_SHARED_QUERY. Lead: Jeff Hammond https://github.com/mpi-forum/mpi-issues/issues/23 <https://github.com/mpi-forum/mpi-issues/issues/23> The WG found support for this and voted 5-1-2 for a full written proposal - Add flush_thread synchronization calls. Lead: Nathan Hjelm No document. Nathan presented this and the WG voted 7-0-2 for a more detailed (e.g., a Powerpoint) description. The WG would like to see the written proposals for generalized atomics and shared_query in time for reading at the December MPI Forum meeting. The WG adjourned after discussing these items. William Gropp Director and Chief Scientist, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign

1 0

Declined:RMA WG Biweekly Telecon
by Sameh S Sharkawi 14 Sep '18

14 Sep '18

1 0

RMA WG recurring telecon
by Balaji, Pavan 14 Sep '18

14 Sep '18

To join the Meeting: https://bluejeans.com/173205081/3141592 To join via Room System: Video Conferencing System: bjn.vc -or-199.48.152.152 Meeting ID : 173205081 Participant Passcode : 3141592 To join via phone : 1) Dial: +1.408.317.9254 (US (San Jose)) +1.866.226.4650 (US Toll Free) (see all numbers - http://bluejeans.com/numbers) 2) Enter Conference ID : 173205081 3) Enter Participant Passcode : 3141592

1 0

RMA WG recurring telecon
by Balaji, Pavan 14 Sep '18

14 Sep '18

Biweekly telecon using Blue Jeans: http://argonne.bluejeans.com/balaji.anl.gov

1 0

Re: [mpiwg-rma] RMA WG recurring telecons
by Balaji, Pavan 14 Sep '18

14 Sep '18

Sorry, folks, that should be 2-3pm central time biweekly starting on 9/24. I've deleted the old entry and created a new one. Sorry for the spam. -- Pavan > On Sep 14, 2018, at 9:49 AM, Balaji, Pavan via mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org> wrote: > > All, > > I've setup RMA WG recurring telecons from 3-4pm central time starting on 9/24. Sorry for the small error in the calendar invite that I have now corrected. If it doesn't show up as a biweekly recurring telecon starting on 9/24, please let me know. > > Thanks, > > -- Pavan > > _______________________________________________ > mpiwg-rma mailing list > mpiwg-rma(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma

1 0