AGENDA - FEB 25, 2026

1. Reconstitution  - subsume partitioned, persistent, point-to-point and collective discussions

2. Items for good of the order form participants not covered below

3. Align with hybrid/streams work in pt2pt scope

BIG PICTURE AGENDA FOR GROUP, NOT EVERYTHING FOR FIRST MEETING.

1. Discuss partitioned collective status and plans

   1. Prior papers

   2. Issues with synchronizing collectives

   3. Prototypes

   4. New ideas with buffer management

   5. Path to standardization

2. Corollary issues with persistent collectives

   1. Non-blocking init/free - not allowed
       

3. Related issue - handoff of control of user state

   1. Handling the registration and registration of index vectors and data pointers

   2. C++ way

   3. C (and Fortran) way with registration callbacks at free

   4. Removing ambiguity in the “zero time use case” and whenever a free is allowed to lazy in MPI that holds user state (so it can be released before MPI_Finalize).

4. Managing unexpected state in partitioned (and maybe persistent) operations

   1. Elimination of PBUF_PREPARE in all partitioned considerations

   2. Considering to “generalize” point-to-point partitioned to enable a) persistence better; b) buffer pools

5. Streaming collectives

6. Other things we “owe” short term

   1. MPI_Parrived_any ticket — very useful with current partitioned point-to-point

7. Document enhancements

   1. Revamping the collective chapter front-to-back (ask Puri if he had some input on prior tries at this?)

   2. Making uniform the presentation of blocking, nonblocking, persistent, and future (partitioned) collective

   3. Front matter needs a look for terms, definitions…

---

Running minutes will be captured and shared.  Recording whenever possible :-)