[mpiwg-persistence] [MPI-Forum] Collective WG meeting today

Wed Feb 25 07:45:45 CST 2026

Dear all,

MPI Collective WG is meeting today in a bit more than one hour.

Please join us to discuss the different topics listed below.

Tony Skjellum (TNTECH) is inviting you to a scheduled Zoom meeting.

Topic: MPI WG Collective (Persistent too)
Time: This is a recurring meeting Meet anytime
Join Zoom Meeting
https://urldefense.us/v3/__https://tntech.zoom.us/j/85895299644?pwd=UVeoehU41wU6tbRKKQIs4ZHpIGphGz.1__;!!G_uCfscf7eWS!fH669uYXAoBNpeVy0rhT2wpQD94rAIvD0AqafTTtL-Qdor0QKqg6fJc93GW_Y63t07XSZR5E-OKaBFdGzsE6Gw8DqtgBzmBvTWsbD7I$ 

Meeting ID: 858 9529 9644
Passcode: mpi4eva

---

One tap mobile
+13017158592,,85895299644#,,,,*2477715# US (Washington DC)
+13052241968,,85895299644#,,,,*2477715# US

Join instructions
https://urldefense.us/v3/__https://tntech.zoom.us/meetings/85895299644/invitations?signature=BzZwXvKEo_bLklZ38Av1D3s0QHwJZZvCadu4btrTcTU__;!!G_uCfscf7eWS!fH669uYXAoBNpeVy0rhT2wpQD94rAIvD0AqafTTtL-Qdor0QKqg6fJc93GW_Y63t07XSZR5E-OKaBFdGzsE6Gw8DqtgBzmBvxVyJHIQ$ 

--------------------------------

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

     *   Prior papers

     *   Issues with synchronizing collectives

     *   Prototypes

     *   New ideas with buffer management

     *   Path to standardization

  2.  Corollary issues with persistent collectives

     *   Non-blocking init/free - not allowed

  3.  Related issue - handoff of control of user state

     *   Handling the registration and registration of index vectors and data pointers

     *   C++ way

     *   C (and Fortran) way with registration callbacks at free

     *   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).

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

     *   Elimination of PBUF_PREPARE in all partitioned considerations

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

  1.  Streaming collectives

  2.  Other things we “owe” short term

     *   MPI_Parrived_any ticket — very useful with current partitioned point-to-point

  3.  Document enhancements

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

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

     *   Front matter needs a look for terms, definitions…

---

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-persistence/attachments/20260225/a66181df/attachment-0001.html>