Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Front matter text clarifications for the "Collective Communication" Chapter #90
Clarifications are needed now that Persistent Communication has been added.
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
Impact on Users
Clarity for users.
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: mpi-forum/mpi-standard#89
referenced this issue
Jun 14, 2018
referenced this issue
Sep 23, 2018
@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.
Here is the latest text, before the two-week deadline, so we can read the ticket. As soon as we fix a make/latex issue with the latest mpi-3.x checkout, the pull request will match this. [I can't build right now, @puribangalore built this from India but could not upload.]
@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.