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

RMA WG Meeting this week
by Joseph Schuchart 18 Oct '23

18 Oct '23

Dear all, After a bit of a break I'd like to meet again to discuss the progress Thomas and I have made on the signalling API. We had a chance to meet in person last week and came up with an interface that combines PSCW and passive target synchronization into a unified API. We'd like to get some feedback on this so we know where to go from here. We'll meet in the usual spot Thursday (October 19) at 10am Central US / 11am Eastern US / 5pm Central Europe. The connection info is as always at https://github.com/mpiwg-rma/mpi-standard/wiki. Please let me know if you cannot access that page so I can add you to the github group. See you there, Joseph

1 0

No meeting today
by Joseph Schuchart 28 Sep '23

28 Sep '23

All, I am swamped with other things and there have not been any new developments beyond the CC fixes for MPI 4.1. Please let me know if you have topics for this or next week's meeting that you want to discuss. Otherwise we'll cancel today and next week. Cheers Joseph

1 0

Re: [mpiwg-rma] RMA chapter review: please review fixes; no meeting today
by Joseph Schuchart 21 Sep '23

21 Sep '23

I have opened https://github.com/mpi-forum/mpi-standard/pull/912 to address the remaining issues. I want to point out two pieces where I would welcome some eyes: 1) "As all \MPI/ \RMA/ communication functions are incomplete, they must be completed": https://github.com/mpi-forum/mpi-standard/pull/912/files#diff-abcde0810b89c… --> I rephrased this to differentiate between procedure and operation. I also added "eventually" to indicate that the completion call can happen at any time after the operation was started. I'm not sure that's the way to phrase it. Maybe it's not necessary. 2) Rule U1 referenced "the following exception". I assume that this was a reference to U2 because only U2 (and no other Rule) would apply as an exception but I want to make sure this is a correct change: https://github.com/mpi-forum/mpi-standard/pull/912/files#diff-abcde0810b89c… Please take a look at the changes and comment on them or approve them as you see fit. With this (and the previous CC changes) we're in good shape for the 4.1 release. I will update the Excel sheet referenced earlier once I get write access. We'll hopefully return to more productive discussions soon :) Many thanks Joseph On 9/21/23 09:18, Joseph Schuchart wrote: > All, > > We've had the MPI Forum meeting last week and have the chapter reviews > from other Forum members in. There were a bunch of minor changes that > should be easy to take on [1] (starting at Line 187). I will try to > fix them this week. Some of them were already addressed in the CC > review PR [2] so this should be easy. > > I don't think we need a meeting over this so I suggest to skip today's > meeting. > > There are three PRs I've opened so far to address what I think are the > most important issues. I would appreciate some reviews by the WG/CC: > (ordered by importance) > > 1) MPI_REQUEST_FREE is not allowed to clean up RMA requests: when > changed the chapter to adapt to the MPI terms we added that > MPI_REQUEST_FREE could be used to release a request after the > operation is known to be completed (i.e., after a flush). However, > that collides with a statement in the above paragraph that > MPI_REQUEST_FREE is not permitted on RMA requests. This is somewhat > annoying but I am hesitant to change the restriction that late in the > 4.1 cycle. The proposed fix is to remove the use of MPI_REQUEST_FREE > from the list of procedures used to release the request: > https://github.com/mpi-forum/mpi-standard/pull/904 > > 2) Remove some explicit mention of MPI-2: there are still explicit > mentions of MPI-2 in the text chapter, which is clearly outdated. The > proposed fix is to rephrase the text to refer to MPI-2 window creation > procedures as the "previously described window creation procedures" > since they appear before the dynamic window creation procedure in the > text: https://github.com/mpi-forum/mpi-standard/pull/905 > > 3) MPI_REPLACE and MPI_NO_OP are not new but additional operators: > this is a rather minor issue but it warrants a fix. The suggested fix > is to replace "new" with "additional": > https://github.com/mpi-forum/mpi-standard/pull/903 > > Thanks for looking at them. The timeline is tight because all changes > for 4.1 must be finalized by September 26. Most of the remaining > issues can probably be wrapped up into a single PR and I will send out > the link once I have that up. > > Many thanks > Joseph > > > [1] > https://docs.google.com/spreadsheets/d/1ZpsyVTnfNHv85K9Mzi_3niNXdmQ67yV2iwS… > [2] https://github.com/mpi-forum/mpi-standard/pull/857

1 0

RMA chapter review: please review fixes; no meeting today
by Joseph Schuchart 21 Sep '23

21 Sep '23

All, We've had the MPI Forum meeting last week and have the chapter reviews from other Forum members in. There were a bunch of minor changes that should be easy to take on [1] (starting at Line 187). I will try to fix them this week. Some of them were already addressed in the CC review PR [2] so this should be easy. I don't think we need a meeting over this so I suggest to skip today's meeting. There are three PRs I've opened so far to address what I think are the most important issues. I would appreciate some reviews by the WG/CC: (ordered by importance) 1) MPI_REQUEST_FREE is not allowed to clean up RMA requests: when changed the chapter to adapt to the MPI terms we added that MPI_REQUEST_FREE could be used to release a request after the operation is known to be completed (i.e., after a flush). However, that collides with a statement in the above paragraph that MPI_REQUEST_FREE is not permitted on RMA requests. This is somewhat annoying but I am hesitant to change the restriction that late in the 4.1 cycle. The proposed fix is to remove the use of MPI_REQUEST_FREE from the list of procedures used to release the request: https://github.com/mpi-forum/mpi-standard/pull/904 2) Remove some explicit mention of MPI-2: there are still explicit mentions of MPI-2 in the text chapter, which is clearly outdated. The proposed fix is to rephrase the text to refer to MPI-2 window creation procedures as the "previously described window creation procedures" since they appear before the dynamic window creation procedure in the text: https://github.com/mpi-forum/mpi-standard/pull/905 3) MPI_REPLACE and MPI_NO_OP are not new but additional operators: this is a rather minor issue but it warrants a fix. The suggested fix is to replace "new" with "additional": https://github.com/mpi-forum/mpi-standard/pull/903 Thanks for looking at them. The timeline is tight because all changes for 4.1 must be finalized by September 26. Most of the remaining issues can probably be wrapped up into a single PR and I will send out the link once I have that up. Many thanks Joseph [1] https://docs.google.com/spreadsheets/d/1ZpsyVTnfNHv85K9Mzi_3niNXdmQ67yV2iwS… [2] https://github.com/mpi-forum/mpi-standard/pull/857

1 0

Re: [mpiwg-rma] RMA Chapter Committee Overview / No meeting today
by Joseph Schuchart 13 Sep '23

13 Sep '23

Thanks Bill, I extended the deck to have the major changes on individual slides. Thanks Joseph On 9/7/23 10:06, Gropp, William D wrote: > > Thanks, Joseph. This is great. On the summary, in the past I’ve > typically separated this into minor edits and improvements (one slide > indicating the PRs and the one line descriptions that you already have > from git) and real changes to the standard (e.g. the new info key, and > probably #708 and #729). > > Bill > > William Gropp > Director, NCSA > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > > *From: *mpiwg-rma <mpiwg-rma-bounces(a)lists.mpi-forum.org> on behalf of > Joseph Schuchart via mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org> > *Date: *Thursday, September 7, 2023 at 8:17 AM > *To: *mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org> > *Cc: *Joseph Schuchart <schuchart(a)icl.utk.edu> > *Subject: *[mpiwg-rma] RMA Chapter Committee Overview / No meeting today > > Dear all, > > I have to cancel today's meeting but I prepared some slides summarizing > the changes to the RMA chapter: > > https://urldefense.com/v3/__https://docs.google.com/presentation/d/14P-uVsV… > <https://urldefense.com/v3/__https:/docs.google.com/presentation/d/14P-uVsVB…> > > > The first slide contains a list of all PRs that affected the chapter, > with the WG changes highlighted. I haven't done such a summary in the > past so I am not sure if this is the right format. If we need more > details I can add slides for each change. Please let me know here or on > Slack if that's the case. Otherwise I will just talk through each of the > changes. > > There is a link to the PDF diff in the slides. The list of CC members is > on the last slide. Please check and let me know if you want to be added > to that list (or taken off in case you're on it). > > I hope to see some of you next week in Bristol! > > Cheers > Joseph > _______________________________________________ > mpiwg-rma mailing list > mpiwg-rma(a)lists.mpi-forum.org > https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… > <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> > >

1 0

Re: [mpiwg-rma] RMA Chapter Committee Overview / No meeting today
by Gropp, William D 07 Sep '23

07 Sep '23

Thanks, Joseph. This is great. On the summary, in the past I’ve typically separated this into minor edits and improvements (one slide indicating the PRs and the one line descriptions that you already have from git) and real changes to the standard (e.g. the new info key, and probably #708 and #729). Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign From: mpiwg-rma <mpiwg-rma-bounces(a)lists.mpi-forum.org> on behalf of Joseph Schuchart via mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org> Date: Thursday, September 7, 2023 at 8:17 AM To: mpiwg-rma <mpiwg-rma(a)lists.mpi-forum.org> Cc: Joseph Schuchart <schuchart(a)icl.utk.edu> Subject: [mpiwg-rma] RMA Chapter Committee Overview / No meeting today Dear all, I have to cancel today's meeting but I prepared some slides summarizing the changes to the RMA chapter: https://urldefense.com/v3/__https://docs.google.com/presentation/d/14P-uVsV…<https://urldefense.com/v3/__https:/docs.google.com/presentation/d/14P-uVsVB…> The first slide contains a list of all PRs that affected the chapter, with the WG changes highlighted. I haven't done such a summary in the past so I am not sure if this is the right format. If we need more details I can add slides for each change. Please let me know here or on Slack if that's the case. Otherwise I will just talk through each of the changes. There is a link to the PDF diff in the slides. The list of CC members is on the last slide. Please check and let me know if you want to be added to that list (or taken off in case you're on it). I hope to see some of you next week in Bristol! Cheers Joseph _______________________________________________ mpiwg-rma mailing list mpiwg-rma(a)lists.mpi-forum.org https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp…<https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…>

1 0

RMA Chapter Committee Overview / No meeting today
by Joseph Schuchart 07 Sep '23

07 Sep '23

Dear all, I have to cancel today's meeting but I prepared some slides summarizing the changes to the RMA chapter: https://docs.google.com/presentation/d/14P-uVsVByJC56mfjWwNskswEuRhKr8JSTj8… The first slide contains a list of all PRs that affected the chapter, with the WG changes highlighted. I haven't done such a summary in the past so I am not sure if this is the right format. If we need more details I can add slides for each change. Please let me know here or on Slack if that's the case. Otherwise I will just talk through each of the changes. There is a link to the PDF diff in the slides. The list of CC members is on the last slide. Please check and let me know if you want to be added to that list (or taken off in case you're on it). I hope to see some of you next week in Bristol! Cheers Joseph

1 0

No RMA WG meeting this week
by Joseph Schuchart 30 Aug '23

30 Aug '23

There is nothing urgent to discuss this week so I suggest we cancel this week's meeting. If you have been assigned pages to review in the standard you can use the time for that instead :) I will start working on the presentation of changes in the RMA chapter for the upcoming MPI Forum meeting and circulate that here but I don't think we need to have a meeting for it. Cheers Joseph

1 0

No RMA WG meeting today
by Joseph Schuchart 24 Aug '23

24 Aug '23

Since things are slow and there is nothing urgent to discuss right now (and the Hot Interconnects is on this week) I suggest we cancel the call today. If we make sufficient progress on the prototype we'll meet again next week. Please let me know if there is anything you want to discuss. Cheers Joseph

1 0

No RMA WG meeting this week
by Joseph Schuchart 03 Aug '23

03 Aug '23

Dear all, I am on vacation for the next two weeks and won't be able to host the RMA WG meeting before August 24. The room is open though, in case people want to meet anyway. Hope everyone has a great summer, Joseph

1 0