Hi all -
Edgar would like to bring the ticket to deprecate the split collective file operations up for a vote at the next File chapter committee working group meeting on Feb. 7 (10-11am US Central time). If you cannot attend that meeting and have questions or would like to vote against moving this forward, please reply on the mailing list, or contact me or Edgar privately. If this passes the vote at the working group meeting, he will submit the change for a reading at the next Forum meeting.
Quincey
> Begin forwarded message:
>
> From: "Gabriel, Edgar" <Edgar.Gabriel(a)amd.com>
> Subject: MPI Forum related items
> Date: January 27, 2025 at 4:45:00 PM CST
> To: Quincey Koziol <qkoziol(a)nvidia.com>
>
> External email: Use caution opening links or attachments
>
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hi Quincey,
>
> Here is a brief write-up for the ‘deprecating split-collective operations’ issue that we should probably vote on in the IO working group:
>
> ----
> This ticket deprecates the split-collective file I/O operations targeting MPI 5.next. From the editorial side, the main change in the document is to move the interface definitions of the split-collective operation to Chapter 17 ‘Deprecated Interfaces’ , and clearly mark all other occurrences of split-collective I/O operations in the document as deprecated, typically by adding the word ‘deprecated’ in parentheses after the occurrence of the function name.
>
> Note that from the conceptual perspective, this PR will deprecate the only non-blocking collective I/O operations on shared file pointers (i.e. MPI_File_{write,read}_ordered_{begin,end}), without introducing replacement for these functions. The rational for this approach is that
>
> i) there are mechanism on how a user can achieve the same functionality through using
> MPI_File_get_position_shared + MPI_Exscan + MPI_File_{iread,iwrite}_at_all + MPI_File_seek_shared
>
> ii) introducing new functions to cover the missing functionality (i.e. MPI_File_{iread,iwrite}_shared_ordered) should be in a separate ticket, if requested by the community.
> ---
>
> ...
>
> Best regards
> Edgar
