Closed RolfRabenseifner closed 1 year ago
I'm moving this to MPI 5.0. If you think we can make this edit as a CC change, we can bring it back in.
The changes of PR 824 are marked with PR824 and also in yellow color on pages 56, 62, 76, 81, 83, 92, 240, 294-296, 310, 497, 626, 688, 804, 810, 1023, 1051, 1052, 1055 in mpi41-report_Issue676_PR824.pdf
The changes of PR 824 are marked with PR824 and also in yellow color on pages 56, 62, 76, 81, 83, 92, 240, 294-296, 310, 497, 626, 688, 804, 810, 1023, 1051, 1052, 1055 in mpi41-report_Issue676_PR824.pdf
There is a counter proposal in PR 825 (see my next comment below).
PR 825 is a counter proposal to PR 824 (for its pdf, see my comment above).
The changes of PR 825 are marked with PR825 and also in yellow color on pages 12, 17, 56, 62, 63, 76, 81, 83, 92, 240, 294-296, 310, 497, 626, 688, 804, 810, 1023, 1051, 1052, 1055 in mpi41-report_Issue676_PR825.pdf
I clearly prefer PR825 because it defines pending (communication) operations. This term exists since MPI-1 and may be used in many software documentations, research papers, book, etc. Therefore, defining pending (communication) operations as "an operation in active state" is better than substituting "pending" by "active".
The results of the virtual MPI forum meeting, June 7, 2023 are
Withdrawing the PR 824, which tried to substitute all "pending operation" by "active operation".
This version v3 of PR 825 includes all proposed changes at the virtual MPI forum meeting, June 7, 2023.
The changes of PR 825 are marked with PR825 and also in yellow color on pages 12, 17, 56, 62, 63, 76, 81, 83, 92, 240, 294-296, 310, 497, 626, 688, 803, 804, 810, 1023, 1051, 1052, 1055 in mpi41-report_Issue676_PR825_v3.pdf
This version v4 includes all proposed changes at the virtual MPI forum meeting, June 7, 2023 together with changes from the review process of this PR 825. The changes are marked with PR825 and also in yellow color on pages 12, 17, 56, 62, 63, 76, 81, 83, 92, 240, 294-296, 310, 497, 626, 688, 803, 804, 810, 1023, 1051, 1052, 1055 in mpi41-report_Issue676_PR825_v4.pdf
PDF files
This passed a errata vote.
Yes | No | Abstain |
32 | 0 | 2 |
Problem
The text uses the term "pending operation" in some places to refer to an "active operation" (as in: it's completion is pending). Nowhere is it defined in what state a pending operation is supposed to be so in some contexts this can be confusing. With semantic terms, the proper term to use differ, for example "active" und "decoupled MPI activities", or soemthing else.
Examples:
§11.10.4
would be
(see also https://github.com/mpi-forum/mpi-issues/issues/536) (may be resolved in https://github.com/mpi-forum/mpi-issues/issues/710)
§6.12:
would be
§7.1.2
would be
§7.4.3
would be
(resolved in https://github.com/mpi-forum/mpi-issues/issues/543)
§... There are many more locations using 'pending'
Proposal
See also solution in issue https://github.com/mpi-forum/mpi-issues/issues/543
One must be careful, because active may be wrong (as in https://github.com/mpi-forum/mpi-issues/issues/543).
Changes to the Text
See above. This should be part of the "cleanup" for MPI 4.1.
Alternatively, the term "pending" could be properly in the terms section. (Risky, because its meaning may be different in different contexts)
Impact on Implementations
None (unless there it renders some implementations non-compliant due to confusion stemming from the usage of the term "pending")
Impact on Users
Clear use of terms helps users better understand the text without having to reason about what a "pending operation" is.
References and Pull Requests