June 2023 - mpi-forum - mailman3.cels.anl.gov

Re: [Mpi-forum] Change-log questions about tools issues in MPI-4.1
by Marc-André Hermanns 30 Jun '23

30 Jun '23

Dear all, as Rolf pointed out to me, this changelog fix needs an individual issue, so I created one here: https://github.com/mpi-forum/mpi-issues/issues/717 Could this be put on the agenda for the July meeting? (even though it's within the 2-week cutoff) Cheers, Marc-Andre On 30.06.23 12:31, Marc-André Hermanns via mpi-forum wrote: > Hi Rolf, > > thanks for double checking this and for the hard work you put into the > preparation of 4.1. > > You might be right that this behavior may imply changes either in an > implementation or in a tool (as any observable behavior will > eventually be relied upon by someone). > > I would therefore agree to a changelog and have opened a PR here: > > https://github.com/mpi-forum/mpi-standard/pull/836 > > Cheers, > Marc-Andre > > On 29.06.23 16:51, Rolf Rabenseifner wrote: >> Dear Marc-Andre and all, >> >> I just checked all MPI-4.1 issues and related pull requests, whether >> (1) they have, >> (2) they have not, but should have, >> (3) they should not have and have not >> a change-log entry. >> >> Problematic is category (2). >> >> I detected the following Issues / PRs and sorted in (1-3): >> >> (3) #160 PR-161 ERRATA: Clarify behavior for invalid MPI_T binding >> arguments > > So here it is (3) -> (2) > >> (1) #443 PR-754 LIS entries in MPI_T chapter not reflecting IN vs. >> INOUT as defined in Term 2.3 chapter >> (3) #542 (PR-646) PR-795 #T Correct usage of the terms error and >> return codes in the tools chapter >> (3) #601 PR-734 Tools - Code examples improperly marked >> (3) #622 PR-734 Tools - Export "outcome is as if..." code fragments >> as proper examples >> (3) #674 PR-796 Tools chapter uses non-standard wildcard-notation >> for function names >> >> As far as I understand, only Issue #160 / PR-161 can be problematic: >> >> Are you sure that #160 does not cause >> - that an implementor of an MPI library has to fix something, or >> - that a user of the tools interface has to modify something in >> her/his tool, >> - or a third party, like trainiers have to change there course >> material? >> >> If there is no such risk, then it is okay to be quiet, i.e. not to >> provide a change-log entry. >> >> I personally expect that there are no such risks and therefore the >> decision "no change-log" was correct. >> >> What is your answer? > > See above. The issue was triggered by a user binding to MPI_COMM_WORLD > "too early" (i.e., before MPI initialization) and therefore at least > that user now needs to change his/her tool. (Even though that might > have been done quite some time ago). > > > If others disagree to this assessment, we can easily bin the > Changelog, if not, we should wordsmith the Changelog entry as > necessary in the July meeting. > > Cheers, > Marc-Andre > > >> ----- Original Message ----- >>> From: "MPI Tool WG" <mpiwg-tools(a)lists.mpi-forum.org> >>> To: "MPI Tool WG" <mpiwg-tools(a)lists.mpi-forum.org> >>> Cc: "Marc-Andre Hermanns" <hermanns(a)itc.rwth-aachen.de> >>> Sent: Thursday, June 29, 2023 1:44:57 PM >>> Subject: [mpiwg-tools] No call today (June 29, 2023) >> >>> Dear all, >>> >>> due to a conflict with another meeting, I would cancel today's >>> meeting. >>> >>> As a teaser for future meetings: Martin brought back >>> feedback/discussion notes from the Scalable Tools Workshop in Tahoe >>> with several topics for us to work on. >>> >>> https://dyninst.github.io/scalable_tools_workshop/petascale2023/assets/slid… >>> >>> Cheers, >>> Marc-Andre >>> -- >>> Dr. rer. nat. Marc-André Hermanns >>> >>> IT Center >>> Group: High Performance Computing >>> Division: Computational Science and Engineering >>> RWTH Aachen University >>> Seffenter Weg 23 >>> 52074 Aachen >>> Phone: +49 241 80-24381 >>> hermanns(a)itc.rwth-aachen.de >>> www.itc.rwth-aachen.de >>> >>> Social Media Kanäle des IT Centers: >>> https://blog.rwth-aachen.de/itc/ >>> https://www.facebook.com/itcenterrwth >>> https://www.linkedin.com/company/itcenterrwth >>> https://twitter.com/ITCenterRWTH >>> https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ >>> >>> _______________________________________________ >>> mpiwg-tools mailing list >>> mpiwg-tools(a)lists.mpi-forum.org >>> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools >> > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de Social Media Kanäle des IT Centers: https://blog.rwth-aachen.de/itc/ https://www.facebook.com/itcenterrwth https://www.linkedin.com/company/itcenterrwth https://twitter.com/ITCenterRWTH https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ

1 0

Re: [Mpi-forum] Change-log questions about tools issues in MPI-4.1
by Marc-André Hermanns 30 Jun '23

30 Jun '23

Hi Rolf, thanks for double checking this and for the hard work you put into the preparation of 4.1. You might be right that this behavior may imply changes either in an implementation or in a tool (as any observable behavior will eventually be relied upon by someone). I would therefore agree to a changelog and have opened a PR here: https://github.com/mpi-forum/mpi-standard/pull/836 Cheers, Marc-Andre On 29.06.23 16:51, Rolf Rabenseifner wrote: > Dear Marc-Andre and all, > > I just checked all MPI-4.1 issues and related pull requests, whether > (1) they have, > (2) they have not, but should have, > (3) they should not have and have not > a change-log entry. > > Problematic is category (2). > > I detected the following Issues / PRs and sorted in (1-3): > > (3) #160 PR-161 ERRATA: Clarify behavior for invalid MPI_T binding arguments So here it is (3) -> (2) > (1) #443 PR-754 LIS entries in MPI_T chapter not reflecting IN vs. INOUT as defined in Term 2.3 chapter > (3) #542 (PR-646) PR-795 #T Correct usage of the terms error and return codes in the tools chapter > (3) #601 PR-734 Tools - Code examples improperly marked > (3) #622 PR-734 Tools - Export "outcome is as if..." code fragments as proper examples > (3) #674 PR-796 Tools chapter uses non-standard wildcard-notation for function names > > As far as I understand, only Issue #160 / PR-161 can be problematic: > > Are you sure that #160 does not cause > - that an implementor of an MPI library has to fix something, or > - that a user of the tools interface has to modify something in her/his tool, > - or a third party, like trainiers have to change there course material? > > If there is no such risk, then it is okay to be quiet, i.e. not to provide a change-log entry. > > I personally expect that there are no such risks and therefore the decision "no change-log" was correct. > > What is your answer? See above. The issue was triggered by a user binding to MPI_COMM_WORLD "too early" (i.e., before MPI initialization) and therefore at least that user now needs to change his/her tool. (Even though that might have been done quite some time ago). If others disagree to this assessment, we can easily bin the Changelog, if not, we should wordsmith the Changelog entry as necessary in the July meeting. Cheers, Marc-Andre > ----- Original Message ----- >> From: "MPI Tool WG" <mpiwg-tools(a)lists.mpi-forum.org> >> To: "MPI Tool WG" <mpiwg-tools(a)lists.mpi-forum.org> >> Cc: "Marc-Andre Hermanns" <hermanns(a)itc.rwth-aachen.de> >> Sent: Thursday, June 29, 2023 1:44:57 PM >> Subject: [mpiwg-tools] No call today (June 29, 2023) > >> Dear all, >> >> due to a conflict with another meeting, I would cancel today's meeting. >> >> As a teaser for future meetings: Martin brought back >> feedback/discussion notes from the Scalable Tools Workshop in Tahoe >> with several topics for us to work on. >> >> https://dyninst.github.io/scalable_tools_workshop/petascale2023/assets/slid… >> >> Cheers, >> Marc-Andre >> -- >> Dr. rer. nat. Marc-André Hermanns >> >> IT Center >> Group: High Performance Computing >> Division: Computational Science and Engineering >> RWTH Aachen University >> Seffenter Weg 23 >> 52074 Aachen >> Phone: +49 241 80-24381 >> hermanns(a)itc.rwth-aachen.de >> www.itc.rwth-aachen.de >> >> Social Media Kanäle des IT Centers: >> https://blog.rwth-aachen.de/itc/ >> https://www.facebook.com/itcenterrwth >> https://www.linkedin.com/company/itcenterrwth >> https://twitter.com/ITCenterRWTH >> https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ >> >> _______________________________________________ >> mpiwg-tools mailing list >> mpiwg-tools(a)lists.mpi-forum.org >> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools > -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de Social Media Kanäle des IT Centers: https://blog.rwth-aachen.de/itc/ https://www.facebook.com/itcenterrwth https://www.linkedin.com/company/itcenterrwth https://twitter.com/ITCenterRWTH https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ

1 0

Re: [Mpi-forum] Ballots for July MPI Forum Meeting
by Rolf Rabenseifner 29 Jun '23

29 Jun '23

Dear Martin and all, > Note: while #379 is for a 2 nd vote, this still needs some discussion whether we > really want to do this or not – comments welcome! The issue #379 with its PR https://github.com/mpi-forum/mpi-standard/pull/737 seems to be not ready for voting: - The PR 737 states [ X ] Check all chapters for potential changes but this is not true. The word "external" exists 172x in the MPI standard (current MPI-4.x). Several of them are related to external interfaces. - The PR 737 is reviewed only by one reviewer and it is unclear whether he checked all the 172 locations of "external". I expect not. - The already mergend issue #645, PR https://github.com/mpi-forum/mpi-standard/pull/767 added new MPI procedures to section 13.3 "Associating Information with Status" which belongs to Chapter 13 "External Interfaces". The new routines are - MPI_Status_set_source, - MPI_Status_set_tag, and - MPI_Status_set_error. The corresponding get procedures are defined in Section 3.2.5. When I understand correctly, these routines are helpful when implementing a new language binding on top of the existing C binding, or for tools. The new chapter name would not fit to this section 13.3. This was already detected by Chhrisoph Niethammer, Feb 8, 2023, see https://github.com/mpi-forum/mpi-standard/pull/737#issuecomment-1422524685 Therefore, I recommend to withdraw this issue from the list for voting. Best regards Rolf ----- Original Message ----- > From: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Sent: Sunday, May 14, 2023 11:52:27 AM > Subject: [Mpi-forum] Ballots for July MPI Forum Meeting > Hi all, > > > > I would like to announce the following ballots for 2 nd votes during our July > meeting: > > > > # 586 , PR 736 : MPI_Buffer_attach and Sessions > > # 685 , PR 808 : Add Iflush procedures to new buffered mode send buffer handling > , > > # 541, PR 647 : Minor edits for consistency in chap-misc > > # 408, PR 740 : Merge or Cross-Reference that Hints must be obeyed by > Application in RMA and Info Chapters > > #478, PR688: Fix Incorrect Usage of Rank/Task/etc. in Process Management Chapter > > # 379 , PR 737 : Rework Intro of External Interfaces Chapter / Possibly Rename > > > > Note: while #379 is for a 2 nd vote, this still needs some discussion whether we > really want to do this or not – comments welcome! > > > > Thanks, > > > > Martin > > > > > > > -- > > Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems > > Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching > > Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) > > Email: schulzm(a)in.tum.de > > > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

No Virtual Meeting this or next week
by Martin Schulz 27 Jun '23

27 Jun '23

Hi all, There will be no virtual meeting this Wednesday or next Wednesday. See you all at the virtual voting meeting, which starts on July 10th. Two quick reminders for this: Please register, if you haven’t done so Please send me plenary or WG time requests – we should have space on the agenda to accommodate this Thanks! Martin -- Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) Email: schulzm(a)in.tum.de

1 0

Sessions WG meeting June 26, 2023 today AND vote announcement for the July 2023 meeting of the MPI Forum
by Rolf Rabenseifner 26 Jun '23

26 Jun '23

Dear all and dear sessions WG, latest update to #710 / PR823 for the voting meeting July 2023: https://github.com/mpi-forum/mpi-standard/files/11866140/mpi41-report_Issue… Further details, please see below. This is also the final input for the sessions WG meeting today !!! new time-slot is Monday 4 PM CEST in Europe = 9 AM CDT in US Please be aware that this proposal still contains 2 orthogonal options (A or B, and without or with C). The Sessions WG meeting today may help to already consolidate - the decision between A or B and/or the - the discision whether withot C or with C. Details of all 4 scheduled errata-reading+votes: __________________________ #710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect Rolf & Sessions WG Issue https://github.com/mpi-forum/mpi-issues/issues/710 PR https://github.com/mpi-forum/mpi-standard/pull/823 PDF from June 26, 2023 https://github.com/mpi-forum/mpi-standard/files/11866140/mpi41-report_Issue… Pre-reading on meeting June 21, 2023: all issues from the reading fixed. Scheduled for errata reading+vote at the July 2023 Forum meeting This issue #710/PR823 contains 4 different proposals, and all 4 proposals are hereby proposed for reading and voting: - With Option A and without Option C, - With Option B and without Option C, - With Option A and with Option C, and - With Option B and with Option C. At the July meeting, it is planned to first do two (orthogonal) staw votes: - whether Option A or B is preferred, and - whether without Option C or with Option C. Based on the result of these two straw votes, only one of the 4 proposals will be presented for the voting of Issue #710/PR823. __________________________ #676 Errata: 'Pending operation' not defined, pending proper definition Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/676 PR https://github.com/mpi-forum/mpi-standard/pull/825 PDF from June 15, 2023: https://github.com/mpi-forum/mpi-standard/files/11760940/mpi41-report_Issue… Defining "pending operation" as "active operation" (see page 12) Pre-reading on meeting June 21, 2023. and errata reading+vote at the July 2023 Forum meeting __________________________ #679 Errata: Noncollective (for procedure) and nonpersistent are not defined Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/679 PR https://github.com/mpi-forum/mpi-standard/pull/820 PDF from May 9, 2023 (last real change from May 2 (pre-reading)) https://github.com/mpi-forum/mpi-standard/files/11432286/mpi41-report_Issue… Pre-reading at May 2, 2023 voting meeting: all issues from the reading fixed. Scheduled for errata reading+vote at the July 2023 Forum meeting __________________________ #705 Errata: Fortran has only compile-time constants Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/705 (together with https://github.com/mpi-forum/mpi-issues/issues/657 Rolf, Jeff H.) PR https://github.com/mpi-forum/mpi-standard/pull/822 PDF from June 20, 2023 https://github.com/mpi-forum/mpi-standard/files/11800606/mpi41-report_Issue… Pre-reading at June 7, 2023 meeting: all issues from the reading fixed. Scheduled for errata reading+vote at the July 2023 Forum meeting Kind regards Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Re: [Mpi-forum] Virtual MPI forum meeting June 21, 2023 / Vote announcement for the July 2023 meeting of the MPI Forum
by Rolf Rabenseifner 20 Jun '23

20 Jun '23

Dear Martin and Wesley and all, (same email as this morning, pdf of #705, PR822 updated, see below) thank you for providing the virtual forum meeting on June 21, 2023. @Wesley and Martin, please can you change in https://www.mpi-forum.org/meetings/2023/07/agenda at Errata Votes, issue #676, the PR 824 into new PR 825. @all, since yesterday, the issue #710, PR 823 is updated by the results from the Sessions WG meeting yesterday. The new PDF is https://github.com/mpi-forum/mpi-standard/files/11793445/mpi41-report_Issue… Both issues are read and discussed tomorrow, June 21, 2023 at the virtual meeting, 10 am CDT in US = 5 pm CEST in Europe Details: __________________________ #710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect Rolf & Sessions WG Issue https://github.com/mpi-forum/mpi-issues/issues/710 PR https://github.com/mpi-forum/mpi-standard/pull/823 PDF from June 19, 2023 https://github.com/mpi-forum/mpi-standard/files/11793445/mpi41-report_Issue… Scheduled for pre-reading on June 21, 2023 and errata reading+vote at the July 2023 Forum meeting __________________________ #676 Errata: 'Pending operation' not defined, pending proper definition Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/676 PR https://github.com/mpi-forum/mpi-standard/pull/825 PDF from June 15, 2023: https://github.com/mpi-forum/mpi-standard/files/11760940/mpi41-report_Issue… Defining "pending operation" as "active operation" (see page 12) Scheduled for pre-reading on June 21, 2023 and errata reading+vote at the July 2023 Forum meeting __________________________ Further pre-read issues scheduled for errata reading+vote at the July 2023 Forum meeting: __________________________ #705 Errata: Fortran has only compile-time constants Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/705 (together with https://github.com/mpi-forum/mpi-issues/issues/657 Rolf, Jeff H.) PR https://github.com/mpi-forum/mpi-standard/pull/822 PDF from June 20, 2023 https://github.com/mpi-forum/mpi-standard/files/11800606/mpi41-report_Issue… Pre-reading at June 7, 2023 meeting: all issues from the reading fixed. Scheduled for errata reading+vote at the July 2023 Forum meeting __________________________ #679 Errata: Noncollective (for procedure) and nonpersistent are not defined Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/679 PR https://github.com/mpi-forum/mpi-standard/pull/820 PDF from May 9, 2023 (last real change from May 2 (pre-reading)) https://github.com/mpi-forum/mpi-standard/files/11432286/mpi41-report_Issue… Pre-reading at May 2, 2023 voting meeting: all issues from the reading fixed. Scheduled for errata reading+vote at the July 2023 Forum meeting Kind regards Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Virtual MPI forum meeting June 21, 2023 / Vote announcement for the July 2023 meeting of the MPI Forum
by Rolf Rabenseifner 20 Jun '23

20 Jun '23

Dear Martin and Wesley and all, thank you for providing the virtual forum meeting on June 21, 2023. @Wesley and Martin, please can you change in https://www.mpi-forum.org/meetings/2023/07/agenda at Errata Votes, issue #676, the PR 824 into new PR 825. @all, since yesterday, the issue #710, PR 823 is updated by the results from the Sessions WG meeting yesterday. The new PDF is https://github.com/mpi-forum/mpi-standard/files/11793445/mpi41-report_Issue… Both issues are read and discussed tomorrow, June 21, 2023 at the virtual meeting, 10 am CDT in US = 5 pm CEST in Europe Details: __________________________ #710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect Rolf & Sessions WG Issue https://github.com/mpi-forum/mpi-issues/issues/710 PR https://github.com/mpi-forum/mpi-standard/pull/823 PDF from June 19, 2023 https://github.com/mpi-forum/mpi-standard/files/11793445/mpi41-report_Issue… Scheduled for pre-reading on June 21, 2023 and errata reading+vote at the July 2023 Forum meeting __________________________ #676 Errata: 'Pending operation' not defined, pending proper definition Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/676 PR https://github.com/mpi-forum/mpi-standard/pull/825 PDF from June 15, 2023: https://github.com/mpi-forum/mpi-standard/files/11760940/mpi41-report_Issue… Defining "pending operation" as "active operation" (see page 12) Scheduled for pre-reading on June 21, 2023 and errata reading+vote at the July 2023 Forum meeting __________________________ Further pre-read issues scheduled for errata reading+vote at the July 2023 Forum meeting: __________________________ #705 Errata: Fortran has only compile-time constants Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/705 (together with https://github.com/mpi-forum/mpi-issues/issues/657 Rolf, Jeff H.) PR https://github.com/mpi-forum/mpi-standard/pull/822 PDF from May 11, 2023 https://github.com/mpi-forum/mpi-standard/files/11450065/mpi41-report_Issue… Pre-reading at June 7, 2023 meeting: - All issues from the reading fixed - One small additional fix in the change-log proposed, already in the pdf and should be committed today in the PR. Then done. Scheduled for errata reading+vote at the July 2023 Forum meeting __________________________ #679 Errata: Noncollective (for procedure) and nonpersistent are not defined Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/679 PR https://github.com/mpi-forum/mpi-standard/pull/820 PDF from May 9, 2023 (last real change from May 2 (reading)) https://github.com/mpi-forum/mpi-standard/files/11432286/mpi41-report_Issue… Pre-reading at May 2, 2023 voting meeting: all issues from the reading fixed. Scheduled for errata reading+vote at the July 2023 Forum meeting Kind regards Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

July Meeting RMA WG vote request
by Joseph Schuchart 18 Jun '23

18 Jun '23

Dear Forum, On behalf of the RMA WG I would to request a second vote on the following MPI-4.1 ticket: *RMA accumulate operations don't distinguish between throughput and latency sensitive applications* Issue: https://github.com/mpi-forum/mpi-issues/issues/640 PR: https://github.com/mpi-forum/mpi-standard/pull/749 Thanks Joseph

1 0

MPI voting announcement
by Holmes, Daniel John 16 Jun '23

16 Jun '23

Hi all, I'm going to go ahead and announce the 2nd vote for the "side documents" proposal. Issue: https://github.com/mpi-forum/mpi-issues/issues/562 PR: https://github.com/mpi-forum/mpi-standard/pull/694 Changes since 1st vote: only chapter committee level tweaks. Best wishes, Dan.

1 0

Re: [Mpi-forum] Virtual MPI forum meeting June 14, 2023 / Vote announcement for the July 2023 meeting of the MPI Forum
by Rolf Rabenseifner 16 Jun '23

16 Jun '23

Dear Martin and Wesley and all, thank you for providing the virtual forum meeting on June 21, 2023. @Wesley and all, the Issue #676 has a changed PR: it is PR825 (previous RP824 is since meeting June 7, 2023 obsolete) Please, can you update this in the July meeting agenda. Details: __________________________ #676 Errata: 'Pending operation' not defined, pending proper definition Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/676 PR https://github.com/mpi-forum/mpi-standard/pull/825 PDF from June 15, 2023: https://github.com/mpi-forum/mpi-standard/files/11760940/mpi41-report_Issue… Defining "pending operation" as "active operation" (see page 12) Scheduled for pre-reding on June 21, 2023 and errata reading+vote at the July 2023 Forum meeting Kind regards Rolf ----- Original Message ----- > From: "Martin Schulz" <schulzm(a)in.tum.de> > To: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de>, "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Cc: "Martin Schulz" <schulzm(a)in.tum.de> > Sent: Wednesday, June 14, 2023 4:32:08 PM > Subject: Re: Virtual MPI forum meeting June 14, 2023 / Vote announcement for the July 2023 meeting of the MPI Forum > Hi Rolf, > > No problem - I added a meeting slot for next week. > > @All: as for this week, let's meet anyway and go over the pending items - this > may be a short meeting, though, as not much seems to be left at this point - > thanks to Wesley, here is the current overview: > > https://github.com/orgs/mpi-forum/projects/1/views/9 > > The meeting is as usual at 10am US CT and the Zoom link is linked from: > > https://github.com/mpi-forum/mpi-standard/wiki/ > > Thanks! > > Martin > > > -- > Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems > Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching > Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) > Email: schulzm(a)in.tum.de > > > > > > >On 14.06.23, 10:10, "Rolf Rabenseifner" <rabenseifner(a)hlrs.de ><mailto:[email protected]>> wrote: > > > Dear all, > > > I just saw that I have a hard conflict today and that I cannot come to the > virtual meeting today. > My apologies. > > > Therefore, I must skip my topics #710/PR823 and #676/PR825 to next week. > I hope that any discussions can already be resolved during this weeek. > If you are interested, please look at the commented pdf files. > > > @Martin, please can you add a virtual meeting for both readings on June 21, > 2023. > > > Kind regards > Rolf > > > ----- Original Message ----- >> From: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org >> <mailto:[email protected]>> >> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org >> <mailto:[email protected]>> >> Sent: Wednesday, June 14, 2023 12:26:11 AM >> Subject: [Mpi-forum] Virtual MPI forum meeting June 14, 2023 / Vote announcement >> for the July 2023 meeting of the MPI >> Forum > > >> Dear MPI forum members, >> >> at the virtual meeting this week (June 14, 2023) on "Any Pending Items for MPI >> 4.1" (Martin) >> I would like to re-read the following proposals: >> >> #710/PR823 clarifying MPI_COMM_DISCONNECT, MPI_FINALIZE and MPI_SESSION_FINALIZE >> with an additional option about inactive persistent requests within a session, >> >> #676/PR825 resolving the missing definition of pending communication operation >> in a hopefully understandable and easy way. >> >> Details: >> >> >> __________________________ >> #710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect Rolf >> Issue https://github.com/mpi-forum/mpi-issues/issues/710 >> <https://github.com/mpi-forum/mpi-issues/issues/710> >> PR https://github.com/mpi-forum/mpi-standard/pull/823 >> <https://github.com/mpi-forum/mpi-standard/pull/823> >> PDF >> https://github.com/mpi-forum/mpi-standard/files/11739843/mpi41-report_Issue… >> <https://github.com/mpi-forum/mpi-standard/files/11739843/mpi41-report_Issue…> >> >> This proposal clarifies MPI_COMM_DISCONNECT, MPI_FINALIZE and >> MPI_SESSION_FINALIZE >> with an additional option about inactive persistent requests within a session. >> >> __________________________ >> #676 Errata: 'Pending operation' not defined, pending proper definition >> Rolf,Joseph >> Issue https://github.com/mpi-forum/mpi-issues/issues/676 >> <https://github.com/mpi-forum/mpi-issues/issues/676> >> PR https://github.com/mpi-forum/mpi-standard/pull/825 >> <https://github.com/mpi-forum/mpi-standard/pull/825> >> PDF >> https://github.com/mpi-forum/mpi-standard/files/11732752/mpi41-report_Issue… >> <https://github.com/mpi-forum/mpi-standard/files/11732752/mpi41-report_Issue…> >> >> Defining "pending operation" as "active operation" (see page 12) >> >> Best regards >> Rolf >> >> >> >> PS: Done already on June 7, 2023: >> >>> __________________________ >>> #705 Errata: Fortran has only compile-time constants Rolf,Joseph >>> Issue https://github.com/mpi-forum/mpi-issues/issues/705 >>> <https://github.com/mpi-forum/mpi-issues/issues/705> >>> (together with https://github.com/mpi-forum/mpi-issues/issues/657 >>> <https://github.com/mpi-forum/mpi-issues/issues/657> Rolf, Jeff >>> H.) >>> PR https://github.com/mpi-forum/mpi-standard/pull/822 >>> <https://github.com/mpi-forum/mpi-standard/pull/822> >>> PDF >>> https://github.com/mpi-forum/mpi-standard/files/11450065/mpi41-report_Issue… >>> <https://github.com/mpi-forum/mpi-standard/files/11450065/mpi41-report_Issue…> >>> >>> This proposal seems to be already stable. >> >> >> ----- Original Message ----- >>> From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de <mailto:[email protected]>> >>> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]>> >>> Cc: "Christoph Niethammer" <niethammer(a)hlrs.de <mailto:[email protected]>>, >>> "Puri Bangalore" >>> <pvbangalore(a)ua.edu <mailto:[email protected]>>, "Joseph Schuchart" >>> <schuchart(a)icl.utk.edu <mailto:[email protected]>> >>> Sent: Wednesday, May 24, 2023 1:36:42 PM >>> Subject: Re: Update: Vote announcement for the July 2023 meeting of the MPI >>> Forum >> >>> Martin, Wes, and all, >>> >>> I expect that we should reserve also June 14, 2023 for a possible continuation >>> of open questions resulting from the discussions of >>> >>>> #705/PR822, #710/PR823, and #676/PR824 are now finalized at least for the >>>> virtual forum meeting, June 7, 2023 >>> >>> and other pending items for MPI-4.1 from the June 7 virtual forum meeting. >>> >>> Best regards >>> Rolf >>> >>> >>> >>> >>> ----- Original Message ----- >>>> From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de <mailto:[email protected]>> >>>> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]>> >>>> Cc: "Christoph Niethammer" <niethammer(a)hlrs.de <mailto:[email protected]>>, >>>> "Puri Bangalore" >>>> <pvbangalore(a)ua.edu <mailto:[email protected]>>, "Joseph Schuchart" >>>> <schuchart(a)icl.utk.edu <mailto:[email protected]>> >>>> Sent: Thursday, May 11, 2023 8:05:07 PM >>>> Subject: Update: Vote announcement for the July 2023 meeting of the MPI Forum >>> >>>> Dear forum members, >>>> >>>> #705/PR822, #710/PR823, and #676/PR824 are now finalized at least for the >>>> virtual forum meeting, June 7, 2023, details below: >>>> >>>> #705 Errata: Fortran has only compile-time constants Rolf,Joseph >>>> Issue https://github.com/mpi-forum/mpi-issues/issues/705 >>>> <https://github.com/mpi-forum/mpi-issues/issues/705> >>>> (together with https://github.com/mpi-forum/mpi-issues/issues/657 >>>> <https://github.com/mpi-forum/mpi-issues/issues/657> Rolf, Jeff >>>> H.) >>>> PR https://github.com/mpi-forum/mpi-standard/pull/822 >>>> <https://github.com/mpi-forum/mpi-standard/pull/822> >>>> PDF >>>> https://github.com/mpi-forum/mpi-standard/files/11450065/mpi41-report_Issue… >>>> <https://github.com/mpi-forum/mpi-standard/files/11450065/mpi41-report_Issue…> >>>> >>>> #710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect Rolf >>>> Issue https://github.com/mpi-forum/mpi-issues/issues/710 >>>> <https://github.com/mpi-forum/mpi-issues/issues/710> >>>> PR https://github.com/mpi-forum/mpi-standard/pull/823 >>>> <https://github.com/mpi-forum/mpi-standard/pull/823> >>>> PDF >>>> https://github.com/mpi-forum/mpi-standard/files/11454896/mpi41-report_Issue… >>>> <https://github.com/mpi-forum/mpi-standard/files/11454896/mpi41-report_Issue…> >>>> >>>> #676 Errata: 'Pending operation' not defined, pending proper definition >>>> Rolf,Joseph >>>> Issue https://github.com/mpi-forum/mpi-issues/issues/676 >>>> <https://github.com/mpi-forum/mpi-issues/issues/676> >>>> PR https://github.com/mpi-forum/mpi-standard/pull/824 >>>> <https://github.com/mpi-forum/mpi-standard/pull/824> >>>> PDF >>>> https://github.com/mpi-forum/mpi-standard/files/11443976/mpi41-report_Issue… >>>> <https://github.com/mpi-forum/mpi-standard/files/11443976/mpi41-report_Issue…> >>>> >>>> The agenda of the virtual meeting should be reading and discussions if needed. >>>> I did the proposals based on the discussion and the major goals: >>>> - backward compatible, >>>> - no performance drawbacks on critical paths, >>>> - full consistency of the solution with all related parts of the MPI standard. >>>> >>>> If I have overseen something, then my apologies. >>>> >>>> If somebody wants to provide a completely different solution to one of these >>>> issues, >>>> please feel free to do it. >>>> - Thanks to Joseph who did PR 822, which was such a counter proposal for #705. >>>> - This method is often better than doing many change requests for the given PR. >>>> and it helps to completely check whether it is really consistent over >>>> all related parts of the MPI standard. >>>> - And thanks for all the comments so far. They really helped me a lot for >>>> preparing the three PRs. >>>> >>>> I'll be the next three weeks on vacation. >>>> >>>> Best regards >>>> Rolf Rabenseifner >>>> >>>> >>>> ----- Original Message ----- >>>>> From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de <mailto:[email protected]>> >>>>> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org >>>>> <mailto:[email protected]>> >>>>> Cc: "Christoph Niethammer" <niethammer(a)hlrs.de <mailto:[email protected]>>, >>>>> "Puri Bangalore" >>>>> <pvbangalore(a)ua.edu <mailto:[email protected]>>, "Joseph Schuchart" >>>>> <schuchart(a)icl.utk.edu <mailto:[email protected]>> >>>>> Sent: Tuesday, May 9, 2023 6:07:04 PM >>>>> Subject: Vote announcement for the July 2023 meeting of the MPI Forum >>>> >>>>> Dear forum members, >>>>> (correction: it is for the July 2023 meeting) >>>>> >>>>> I would like to make the following announcements for the next MPI Forum Meeting >>>>> (July 10-13, 2023): >>>>> >>>>> - 2nd votes on >>>>> #669 Add operation state 'enabled' and 'local calls' into Terms Rolf >>>>> Issue https://github.com/mpi-forum/mpi-issues/issues/669 >>>>> <https://github.com/mpi-forum/mpi-issues/issues/669> >>>>> PR https://github.com/mpi-forum/mpi-standard/pull/788 >>>>> <https://github.com/mpi-forum/mpi-standard/pull/788> >>>>> >>>>> #457 Improvements around the word "rank" in the Process Topologies chapter >>>>> Christoph,Rolf >>>>> Issue https://github.com/mpi-forum/mpi-issues/issues/457 >>>>> <https://github.com/mpi-forum/mpi-issues/issues/457> >>>>> PR https://github.com/mpi-forum/mpi-standard/pull/804 >>>>> <https://github.com/mpi-forum/mpi-standard/pull/804> >>>>> >>>>> #485 Fix Incorrect Usage of Rank/Task/etc. in Language Bindings Chapter >>>>> Rolf,Puri >>>>> Issue https://github.com/mpi-forum/mpi-issues/issues/485 >>>>> <https://github.com/mpi-forum/mpi-issues/issues/485> >>>>> PR https://github.com/mpi-forum/mpi-standard/pull/803 >>>>> <https://github.com/mpi-forum/mpi-standard/pull/803> >>>>> PDF >>>>> https://github.com/mpi-forum/mpi-standard/files/10831598/mpi41-report_Issue… >>>>> <https://github.com/mpi-forum/mpi-standard/files/10831598/mpi41-report_Issue…> >>>>> >>>>> - errata reading and vote on >>>>> >>>>> #679 Errata: Noncollective (for procedure) and nonpersistent are not defined >>>>> Rolf >>>>> Issue https://github.com/mpi-forum/mpi-issues/issues/679 >>>>> <https://github.com/mpi-forum/mpi-issues/issues/679> >>>>> PR https://github.com/mpi-forum/mpi-standard/pull/820 >>>>> <https://github.com/mpi-forum/mpi-standard/pull/820> >>>>> PDF >>>>> https://github.com/mpi-forum/mpi-standard/files/11432286/mpi41-report_Issue… >>>>> <https://github.com/mpi-forum/mpi-standard/files/11432286/mpi41-report_Issue…> >>>>> >>>>> - pre-announcement for errata reading and vote on >>>>> --> See also virtual meeting, June 7, 2023 !!! >>>>> >>>>> #705 Errata: Fortran has only compile-time constants Rolf,Joseph >>>>> Issue https://github.com/mpi-forum/mpi-issues/issues/705 >>>>> <https://github.com/mpi-forum/mpi-issues/issues/705> >>>>> (together with https://github.com/mpi-forum/mpi-issues/issues/657 >>>>> <https://github.com/mpi-forum/mpi-issues/issues/657> Rolf, Jeff >>>>> H.) >>>>> PR https://github.com/mpi-forum/mpi-standard/pull/822 >>>>> <https://github.com/mpi-forum/mpi-standard/pull/822> >>>>> >>>>> #710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect Rolf >>>>> Issue https://github.com/mpi-forum/mpi-issues/issues/710 >>>>> <https://github.com/mpi-forum/mpi-issues/issues/710> >>>>> PR https://github.com/mpi-forum/mpi-standard/pull/823 >>>>> <https://github.com/mpi-forum/mpi-standard/pull/823> >>>>> >>>>> #676 Errata: 'Pending operation' not defined, pending proper definition >>>>> Rolf,Joseph >>>>> Issue https://github.com/mpi-forum/mpi-issues/issues/676 >>>>> <https://github.com/mpi-forum/mpi-issues/issues/676> >>>>> PR https://github.com/mpi-forum/mpi-standard/pull/824 >>>>> <https://github.com/mpi-forum/mpi-standard/pull/824> >>>>> >>>>> Best regards >>>>> Rolf Rabenseifner >> >> >> -- >> Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de >> <mailto:[email protected]> . >> High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . >> University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . >> Nobelstr. 19, 70569 Stuttgart, Germany >> _______________________________________________ >> mpi-forum mailing list >> mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]> >> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum >> <https://lists.mpi-forum.org/mailman/listinfo/mpi-forum> > > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de > <mailto:[email protected]> . > High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . > University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . > Nobelstr. 19, 70569 Stuttgart, Germany -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0