Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reorganizing the "Collective Communication" Chapter #90

Open
tonyskjellum opened this issue Mar 21, 2018 · 15 comments
Open

Reorganizing the "Collective Communication" Chapter #90

tonyskjellum opened this issue Mar 21, 2018 · 15 comments
Assignees
Labels
mpi-5 For inclusion in the MPI 5.0 standard wg-collectives Collectives Working Group wg-persistence Persistence Working Group

Comments

@tonyskjellum
Copy link

tonyskjellum commented Mar 21, 2018

Problem

Clarifications are needed now that Persistent Communication has been added.

Proposal

Persistent communication addition has raised the need for clarifying text. This definitely applies to the Collective chapter

Changes to the Text

Chapter 5 (Collective Chapter) -- updated appropriately.

Impact on Implementations

None.

Impact on Users

Clarity for users.

References

Ticket #25 [which has passed 2 votes now] is driving this requirement, but we want to settle this concern separately as agreed in Forum meetings.

Here is the corresponding pull request: https://github.com/mpi-forum/mpi-standard/pull/89
(This is a revised pull requested as of 19-Nov-18)

@dholmes-epcc-ed-ac-uk dholmes-epcc-ed-ac-uk added mpi <next> wg-persistence Persistence Working Group wg-collectives Collectives Working Group labels Mar 21, 2018
@tonyskjellum tonyskjellum added mpi-4.0 scheduled reading Reading is scheduled for the next meeting and removed mpi <next> labels May 23, 2018
@tonyskjellum
Copy link
Author

mpi32-report-ticket90.pdf

This copy is public.

@tonyskjellum
Copy link
Author

tonyskjellum commented Jun 14, 2018

A review was done on June 13, 2018 at the MPI meeting in Austin. Updates will be made and a reading will be presented in Barcelona.

@tonyskjellum
Copy link
Author

@puribangalore --- Please look at Ticket #80; the latest update adds _X APIs for the persistent collectives; in the process, I've had to go back and enumerate both persistent and persistent _X operations where they have failed to be named throughout Chapter 5. This has got to be related to editorial changes you've been undertaking or plan to do here. In fact, we need to correlate those changes. Ticket #105 will likewise do a review of function enumeration once we add the _X APIs later this week.

@tonyskjellum
Copy link
Author

@puribangalore --- we need to update this for the meeting next Thursday ... we need to finish before November 10! We will present in San Jose... do you need help?

@tonyskjellum

This comment has been minimized.

@tonyskjellum
Copy link
Author

Here's the text we actually want you to read for the two-week deadline review:

mpi32-report-ticket90-19nov18.pdf

@tonyskjellum
Copy link
Author

@puribangalore read the chapter; there was various feedback of a general nature.

For instance, issues with commas and capitalization (already addressed to first order).

However, by strawpoll, we voted to reorganize the chapter so that "All Barrier, "All Broadcast," ... "All Exscan." is the order, rather than a parallel section Blocking, Nonblocking, and Persistent. That will necessarily "transpose the 3 sections of operations, and move ahead the discussions, so that the operations will all be "together." This mirror the topologies and other chapters better. This is meant to be part of this ticket... and a careful review is required to be sure we don't change any meanings. That is not supposed to happen just by reordering presentation of the APIs. @puribangalore and @tonyskjellum will do this reordering task and present in Chattanooga in March.

@tonyskjellum tonyskjellum changed the title Front matter text clarifications for the "Collective Communication" and "Topology" Chapters Front matter text clarifications for the "Collective Communication" Chapter Dec 12, 2018
@tonyskjellum
Copy link
Author

We did not do the recommended steps for Chattanooga. We are revisiting this task for Chicago.

@tonyskjellum
Copy link
Author

Aiming for MPI-4.1 because it is "text tidying." We will wait till all MPI-4.0 work is done before revisiting this.

@wesbland wesbland added mpi-4.1 For inclusion in the MPI 4.1 standard and removed mpi-4.0 labels Oct 8, 2020
@Wee-Free-Scot
Copy link

This needs to move very quickly if it is going to hit MPI-4.1 -- who is working on it?

@Wee-Free-Scot Wee-Free-Scot removed their assignment Oct 20, 2022
@wesbland
Copy link
Member

wesbland commented Dec 8, 2022

This wasn't read at the December 2022 meeting. The last opportunity for MPI 4.1 is to have it ready at the March 2022 meeting (and it needs to "pass" the reading).

@tonyskjellum / @puribangalore Are you (or is someone else) planning to push this forward or should we move it out of the plan for MPI 4.1?

@jaegerj jaegerj self-assigned this Feb 22, 2023
@jaegerj
Copy link
Member

jaegerj commented Feb 22, 2023

This won't be ready for 4.1 but can be targeted to MPI 5.0.

The title does not fit the content of the ticket anymore.
Some clarifications have already been made, and another ticket exist to focus on the indroductory text of the collective chapter (#256 -- which also should be rename with the current title of this ticket ironically)

The main part of the ticket which has not been handled yet is the reorganizing of the collective chapter.
Maybe we should rename this ticket accordingly.

@wesbland wesbland added mpi-5 For inclusion in the MPI 5.0 standard and removed mpi-4.1 For inclusion in the MPI 4.1 standard labels Feb 23, 2023
@wesbland
Copy link
Member

@jaegerj - You're welcome to rename the ticket to anything you like. :)

@jaegerj
Copy link
Member

jaegerj commented Feb 23, 2023

@tonyskjellum @puribangalore would it be ok with you to rename this ticket "Reorganizing the collective chapter" ?

@puribangalore
Copy link

puribangalore commented Feb 23, 2023 via email

@jaegerj jaegerj changed the title Front matter text clarifications for the "Collective Communication" Chapter Reorganizing the "Collective Communication" Chapter Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mpi-5 For inclusion in the MPI 5.0 standard wg-collectives Collectives Working Group wg-persistence Persistence Working Group
Projects
Status: To Do
Development

No branches or pull requests

6 participants