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

Re: [mpiwg-rma] MPI RMA WG call
by William Gropp 28 Aug '21

28 Aug '21

I have no objections to someone else taking the lead. We did try to find a good time for a meeting, but I don’t think that we succeeded, and I didn’t restart the search in August, and agreeing on a time remains the first thing to resolve. Just to get this restarted, would 10-11 US Central time on Tuesday work? Keep in mind these constraints - for the US West coast, we try to start no earlier than 8PT/10CT. For Europe, we try to end by 6 CET, which is noon US CT. Let me know if that time works. If it doesn’t suggest something in the range above. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign IEEE-CS President-Elect > On Aug 28, 2021, at 10:28 AM, Jim Dinan <james.dinan(a)gmail.com> wrote: > > I have not seen such an announcement. I think this WG is in need of someone to take the lead on organizing meetings and topics. If you have the bandwidth to get us moving, I think the help would be very much appreciated. @William Gropp <mailto:[email protected]> What do you think? > > Cheers, > ~Jim. > > On Wed, Aug 25, 2021 at 12:01 PM Joseph Schuchart via mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org <mailto:[email protected]>> wrote: > Hi Bill, all, > > Has there been a decision on when to reconvene the RMA working group? I > recently changed institutes and might have missed emails sent to my old > address... > > Thanks, > Joseph > > On 6/15/21 11:10 AM, William Gropp via mpiwg-rma wrote: > > Hi everyone, > > > > It's been a long time since we’ve had an RMA call, and there are many > > open topics that we need to discuss. Specifically, Min Si has raised > > the issue of generalized RMA atomics, in this ticket and PR: > > > > Ticket: https://github.com/mpi-forum/mpi-issues/issues/114 <https://urldefense.com/v3/__https://github.com/mpi-forum/mpi-issues/issues/…> > > <https://github.com/mpi-forum/mpi-issues/issues/114 <https://urldefense.com/v3/__https://github.com/mpi-forum/mpi-issues/issues/…>> > > PR: https://github.com/mpi-forum/mpi-standard/pull/93 <https://urldefense.com/v3/__https://github.com/mpi-forum/mpi-standard/pull/…> > > <https://github.com/mpi-forum/mpi-standard/pull/93 <https://urldefense.com/v3/__https://github.com/mpi-forum/mpi-standard/pull/…>> > > > > I’d like to schedule at least one RMA call, and allow for a regular set > > of calls until we’ve handled the open RMA issues. So my first questions > > are (a) are you interested in participating and if so (b) would sometime > > mid-morning US (9-11 CDT) work? If so, the next step will be a doodle > > poll to find a specific regular time. Please let my assistant, Stacy > > Walker cc’ed above, know if you want to participate. > > > > Bill > > > > William Gropp > > Director, NCSA > > Thomas M. Siebel Chair in Computer Science > > University of Illinois Urbana-Champaign > > IEEE-CS President-Elect > > > > > > > > > > > > _______________________________________________ > > mpiwg-rma mailing list > > mpiwg-rma(a)lists.mpi-forum.org <mailto:[email protected]> > > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma <https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp…> > > > _______________________________________________ > mpiwg-rma mailing list > mpiwg-rma(a)lists.mpi-forum.org <mailto:[email protected]> > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma <https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp…>

1 0

Re: [mpiwg-rma] MPI RMA WG call
by Jim Dinan 28 Aug '21

28 Aug '21

I have not seen such an announcement. I think this WG is in need of someone to take the lead on organizing meetings and topics. If you have the bandwidth to get us moving, I think the help would be very much appreciated. @William Gropp <wgropp(a)illinois.edu> What do you think? Cheers, ~Jim. On Wed, Aug 25, 2021 at 12:01 PM Joseph Schuchart via mpiwg-rma < mpiwg-rma(a)lists.mpi-forum.org> wrote: > Hi Bill, all, > > Has there been a decision on when to reconvene the RMA working group? I > recently changed institutes and might have missed emails sent to my old > address... > > Thanks, > Joseph > > On 6/15/21 11:10 AM, William Gropp via mpiwg-rma wrote: > > Hi everyone, > > > > It's been a long time since we’ve had an RMA call, and there are many > > open topics that we need to discuss. Specifically, Min Si has raised > > the issue of generalized RMA atomics, in this ticket and PR: > > > > Ticket: https://github.com/mpi-forum/mpi-issues/issues/114 > > <https://github.com/mpi-forum/mpi-issues/issues/114> > > PR: https://github.com/mpi-forum/mpi-standard/pull/93 > > <https://github.com/mpi-forum/mpi-standard/pull/93> > > > > I’d like to schedule at least one RMA call, and allow for a regular set > > of calls until we’ve handled the open RMA issues. So my first questions > > are (a) are you interested in participating and if so (b) would sometime > > mid-morning US (9-11 CDT) work? If so, the next step will be a doodle > > poll to find a specific regular time. Please let my assistant, Stacy > > Walker cc’ed above, know if you want to participate. > > > > Bill > > > > William Gropp > > Director, NCSA > > Thomas M. Siebel Chair in Computer Science > > University of Illinois Urbana-Champaign > > IEEE-CS President-Elect > > > > > > > > > > > > _______________________________________________ > > 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

Re: [mpiwg-rma] MPI RMA WG call
by Joseph Schuchart 25 Aug '21

25 Aug '21

Hi Bill, all, Has there been a decision on when to reconvene the RMA working group? I recently changed institutes and might have missed emails sent to my old address... Thanks, Joseph On 6/15/21 11:10 AM, William Gropp via mpiwg-rma wrote: > Hi everyone, > > It's been a long time since we’ve had an RMA call, and there are many > open topics that we need to discuss. Specifically, Min Si has raised > the issue of generalized RMA atomics, in this ticket and PR: > > Ticket: https://github.com/mpi-forum/mpi-issues/issues/114 > <https://github.com/mpi-forum/mpi-issues/issues/114> > PR: https://github.com/mpi-forum/mpi-standard/pull/93 > <https://github.com/mpi-forum/mpi-standard/pull/93> > > I’d like to schedule at least one RMA call, and allow for a regular set > of calls until we’ve handled the open RMA issues. So my first questions > are (a) are you interested in participating and if so (b) would sometime > mid-morning US (9-11 CDT) work? If so, the next step will be a doodle > poll to find a specific regular time. Please let my assistant, Stacy > Walker cc’ed above, know if you want to participate. > > Bill > > William Gropp > Director, NCSA > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > IEEE-CS President-Elect > > > > > > _______________________________________________ > mpiwg-rma mailing list > mpiwg-rma(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma >

1 0

Re: [mpiwg-rma] MPI RMA WG call
by Min Si 17 Jun '21

17 Jun '21

Hi Bill, 9-11 CDT works for me too. My Argonne email address is temporarily invalid. That was why you see delayed response from me. I am CCing Yanfei@Argonne within this thread so he is aware of it. Best regards, Min On 6/15/21 5:10 PM, William Gropp via mpiwg-rma wrote: >/Hi everyone, />//>/It's been a long time since we’ve had an RMA call, and there are many />/open topics that we need to discuss. Specifically, Min Si has raised />/the issue of generalized RMA atomics, in this ticket and PR: />//>/Ticket: https://github.com/mpi-forum/mpi-issues/issues/114 <https://github.com/mpi-forum/mpi-issues/issues/114> />/<https://github.com/mpi-forum/mpi-issues/issues/114 <https://github.com/mpi-forum/mpi-issues/issues/114>> />/PR: https://github.com/mpi-forum/mpi-standard/pull/93 <https://github.com/mpi-forum/mpi-standard/pull/93> />/<https://github.com/mpi-forum/mpi-standard/pull/93 <https://github.com/mpi-forum/mpi-standard/pull/93>> />//>/I’d like to schedule at least one RMA call, and allow for a regular set />/of calls until we’ve handled the open RMA issues. So my first questions />/are (a) are you interested in participating and if so (b) would sometime />/mid-morning US (9-11 CDT) work? If so, the next step will be a doodle />/poll to find a specific regular time. Please let my assistant, Stacy />/Walker cc’ed above, know if you want to participate. />//>/Bill />//>/William Gropp />/Director, NCSA />/Thomas M. Siebel Chair in Computer Science />/University of Illinois Urbana-Champaign />/IEEE-CS President-Elect />//

1 0

Re: [mpiwg-rma] MPI RMA WG call
by Joseph Schuchart 16 Jun '21

16 Jun '21

Hi Bill, all, I was planning to revive the RMA meetings but you beat me to it ^^ 9-11 CDT works for me Mondays and Tuesdays. Later in the day would be no problem for me. Thanks Joseph On 6/15/21 5:10 PM, William Gropp via mpiwg-rma wrote: > Hi everyone, > > It's been a long time since we’ve had an RMA call, and there are many > open topics that we need to discuss. Specifically, Min Si has raised > the issue of generalized RMA atomics, in this ticket and PR: > > Ticket: https://github.com/mpi-forum/mpi-issues/issues/114 > <https://github.com/mpi-forum/mpi-issues/issues/114> > PR: https://github.com/mpi-forum/mpi-standard/pull/93 > <https://github.com/mpi-forum/mpi-standard/pull/93> > > I’d like to schedule at least one RMA call, and allow for a regular set > of calls until we’ve handled the open RMA issues. So my first questions > are (a) are you interested in participating and if so (b) would sometime > mid-morning US (9-11 CDT) work? If so, the next step will be a doodle > poll to find a specific regular time. Please let my assistant, Stacy > Walker cc’ed above, know if you want to participate. > > Bill > > William Gropp > Director, NCSA > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > IEEE-CS President-Elect > > > > > > _______________________________________________ > mpiwg-rma mailing list > mpiwg-rma(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma >

1 0

Re: [mpiwg-rma] MPI RMA WG call
by Jim Dinan 15 Jun '21

15 Jun '21

Hi Bill, I would be happy to join the discussions. 9-11 CDT is no problem from my time zone. ~Jim. On Tue, Jun 15, 2021 at 11:10 AM William Gropp via mpiwg-rma < mpiwg-rma(a)lists.mpi-forum.org> wrote: > Hi everyone, > > It's been a long time since we’ve had an RMA call, and there are many open > topics that we need to discuss. Specifically, Min Si has raised the issue > of generalized RMA atomics, in this ticket and PR: > > Ticket: https://github.com/mpi-forum/mpi-issues/issues/114 > PR: https://github.com/mpi-forum/mpi-standard/pull/93 > > I’d like to schedule at least one RMA call, and allow for a regular set of > calls until we’ve handled the open RMA issues. So my first questions are > (a) are you interested in participating and if so (b) would sometime > mid-morning US (9-11 CDT) work? If so, the next step will be a doodle poll > to find a specific regular time. Please let my assistant, Stacy Walker > cc’ed above, know if you want to participate. > > Bill > > William Gropp > Director, NCSA > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > IEEE-CS President-Elect > > > > > _______________________________________________ > mpiwg-rma mailing list > mpiwg-rma(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-rma >

1 0

MPI RMA WG call
by William Gropp 15 Jun '21

15 Jun '21

Hi everyone, It's been a long time since we’ve had an RMA call, and there are many open topics that we need to discuss. Specifically, Min Si has raised the issue of generalized RMA atomics, in this ticket and PR: Ticket: https://github.com/mpi-forum/mpi-issues/issues/114 <https://github.com/mpi-forum/mpi-issues/issues/114> PR: https://github.com/mpi-forum/mpi-standard/pull/93 <https://github.com/mpi-forum/mpi-standard/pull/93> I’d like to schedule at least one RMA call, and allow for a regular set of calls until we’ve handled the open RMA issues. So my first questions are (a) are you interested in participating and if so (b) would sometime mid-morning US (9-11 CDT) work? If so, the next step will be a doodle poll to find a specific regular time. Please let my assistant, Stacy Walker cc’ed above, know if you want to participate. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign IEEE-CS President-Elect

1 0

Re: [mpiwg-rma] Bugs in RMA in current MPI standard - Re: Summary of MPI RMA WG meeting on Sept 21, 2018
by Rolf Rabenseifner 19 Feb '19

19 Feb '19

Dear Pavan and all, I just found the ticket from Bill, Sep. 19, 2016 and labeled it with wg-rma, MPI-4.0, Chattanooga, reading. Still within Monday Feb. 18, 2019 deadline for Chattanooga when using Hawaiian timezone ;-) Therefore, I'll also send out the Forum-Mail for the reading before midnight on Hawaii. I hope, that this is okay for you all. The further going solution, as proposed by Pavan should be discussed independently, because also allowing MPI_Win_create, i.e., removing the whole restriction, may have Performance aspects if the progress implementation of an MPI library is not identical for MPI_Win_create and MPI_Win_create_dynamic + MPI_Win_attach. Pavan, I hope that you can add the pull request for this ticket today. As change-log, I propose \item Section~\ref{sec:1sided-lock} on page~\pageref{sec:1sided-lock}. \newline The rule that implementors may restrict the use of \RMA/ communication that is synchronized with \mpifunc{MPI\_WIN\_LOCK}, \mpifunc{MPI\_WIN\_LOCK\_ALL} and other lock calls to windows in memory allocated by \mpifunc{MPI\_ALLOC\_MEM}, \mpifunc{MPI\_WIN\_ALLOCATE}, or attached with \mpifunc{MPI\_WIN\_ATTACH}, is extended by memory allocated with \mpifunc{MPI\_WIN\_ALLOCATE\_SHARED}. ---- With this, we have the change-log also visible in the index entry of all related routines, which helps that people can find the change-log. Best regards Rolf ----- Original Message ----- > From: "MPI WG Remote Memory Access working group" <mpiwg-rma(a)lists.mpi-forum.org> > To: "Pavan Balaji" <balaji(a)anl.gov> > Cc: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de>, "MPI WG Remote Memory Access working group" > <mpiwg-rma(a)lists.mpi-forum.org> > Sent: Sunday, February 17, 2019 1:15:53 PM > Subject: Re: [mpiwg-rma] Bugs in RMA in current MPI standard - Re: Summary of MPI RMA WG meeting on Sept 21, 2018 >> +1 on removing that text. The intent was to allow Win_create too, which we >> somehow missed. > The original MPI-2 intent was, to allow only memories that were allocated by > an MPI library routine and ***not*** just handed over by the user (as with > MPI_WIN_CREATE). > This means, MPI_WIN_CREATE was originally never intented. > > In MPI-2, it was therefore only MPI_ALLOC_MEM. > I do not understand, why MPI_WIN_ATTACH was added to the list. > And I expect that MPI_WIN_ALLOCATE_SHARED was overseen. > But as Jeff said, with MPI_WIN_ATTACH in the list, > this restriction does not make sense anymore. > > Is there a ticket resolving this Problem in MPI-4.0 > (Deadline seems to be today (or Monday noon?). > > Best regards > Rolf > > ----- Original Message ----- >> From: "Pavan Balaji" <balaji(a)anl.gov> >> To: "MPI WG Remote Memory Access working group" <mpiwg-rma(a)lists.mpi-forum.org> >> Cc: "Pavan Balaji" <balaji(a)anl.gov>, "Rolf Rabenseifner" <rabenseifner(a)hlrs.de>, >> "Jeff Hammond" <jeff.science(a)gmail.com> >> Sent: Wednesday, September 26, 2018 6:16:25 PM >> Subject: Re: [mpiwg-rma] Bugs in RMA in current MPI standard - Re: Summary of >> MPI RMA WG meeting on Sept 21, 2018 > >>> On Sep 25, 2018, at 9:38 PM, Jeff Hammond via mpiwg-rma >>> <mpiwg-rma(a)lists.mpi-forum.org> wrote: >>> 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. >>> >>> >>> >>> I am not certain that this change is consistent with the original intent, but we >>> should just remove this text, because it does not make sense anymore. If >>> MPI_Win_attach is sufficient to allow locks, then MPI_Win_create should be >>> there, because one can implement MPI_Win_create in terms of >>> MPI_Win_create_dynamic+MPI_Win_attach. >> >> +1 on removing that text. The intent was to allow Win_create too, which we >> somehow missed. >> >> -- Pavan > > -- > 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) . > _______________________________________________ > 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] Bugs in RMA in current MPI standard - Re: Summary of MPI RMA WG meeting on Sept 21, 2018
by Rolf Rabenseifner 17 Feb '19

17 Feb '19

> +1 on removing that text. The intent was to allow Win_create too, which we > somehow missed. The original MPI-2 intent was, to allow only memories that were allocated by an MPI library routine and ***not*** just handed over by the user (as with MPI_WIN_CREATE). This means, MPI_WIN_CREATE was originally never intented. In MPI-2, it was therefore only MPI_ALLOC_MEM. I do not understand, why MPI_WIN_ATTACH was added to the list. And I expect that MPI_WIN_ALLOCATE_SHARED was overseen. But as Jeff said, with MPI_WIN_ATTACH in the list, this restriction does not make sense anymore. Is there a ticket resolving this Problem in MPI-4.0 (Deadline seems to be today (or Monday noon?). Best regards Rolf ----- Original Message ----- > From: "Pavan Balaji" <balaji(a)anl.gov> > To: "MPI WG Remote Memory Access working group" <mpiwg-rma(a)lists.mpi-forum.org> > Cc: "Pavan Balaji" <balaji(a)anl.gov>, "Rolf Rabenseifner" <rabenseifner(a)hlrs.de>, "Jeff Hammond" <jeff.science(a)gmail.com> > Sent: Wednesday, September 26, 2018 6:16:25 PM > Subject: Re: [mpiwg-rma] Bugs in RMA in current MPI standard - Re: Summary of MPI RMA WG meeting on Sept 21, 2018 >> On Sep 25, 2018, at 9:38 PM, Jeff Hammond via mpiwg-rma >> <mpiwg-rma(a)lists.mpi-forum.org> wrote: >> 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. >> >> >> >> I am not certain that this change is consistent with the original intent, but we >> should just remove this text, because it does not make sense anymore. If >> MPI_Win_attach is sufficient to allow locks, then MPI_Win_create should be >> there, because one can implement MPI_Win_create in terms of >> MPI_Win_create_dynamic+MPI_Win_attach. > > +1 on removing that text. The intent was to allow Win_create too, which we > somehow missed. > > -- Pavan -- 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

Canceled: RMA WG recurring telecon
by Balaji, Pavan 29 Dec '18

29 Dec '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