You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: MPI_Next_main_page.md
+119-2Lines changed: 119 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,126 @@ The forum encourages that new items will be brought forward through the respecti
13
13
14
14
## Active Working Groups
15
15
16
-
The working groups that are currently participating in the MPI efforts are listed on the page for MPI 5.0.
16
+
The following working groups are currently participating in future MPI efforts. For more information on each working group, current topics, and meeting schedules, please follow the links to the respective Wiki pages.
* Scope: The purpose of the MPI ABI Working Group is to discuss and implement the features required for MPI binaries - applications and libraries - to work with any implementation of MPI on compatible platforms.
* Lead: Anthony Skjellum and Julien Jaeger (prior leads: Torsten Hoefler, Andrew Lumsdaine)
27
+
* Scope: This working group considers cross-cutting issues of groups, context, communicators, and collective operations as well as features such as persistence, partitioning, topologies, and operational semantics (e.g., blocking, nonblocking, local, synchronizing) thereof.
28
+
* Meeting Schedule: Wednesdays at <ahref="https://time.is/0900_in_CT">9am</a> US Central Time
* Scope: To define any additional support needed in the MPI standard to enable implementation of portable Fault Tolerant solutions for MPI based applications.
34
+
* Meeting Schedule: Fortnightly on Mondays at <ahref="https://time.is/900_in_CT">9am</a> US Central Time
* Scope: Address questions like how can hardware resources (I/O, cores, caches, I/O proxies, etc.) be discovered, queried upon and distributed between execution flows? Define portable primitives inside MPI to explore and take advantage of the hardware topology either at the node or the process level.
* Scope: Ensure that MPI has the features necessary to facilitate efficient hybrid programming and investigate what changes are needed in MPI to better support traditional thread interfaces (e.g., Pthreads, OpenMP), emerging interfaces (like TBB, OpenCL, CUDA, and Ct), and PGAS (UPC, CAF, etc.).
53
+
* Meeting Schedule: Wednesdays at <ahref="https://time.is/0900_in_CT">9am</a> US Central Time
54
+
55
+
#### [I/O](https://github.com/mpiwg-io/)
56
+
57
+
* Lead: Quincey Koziol
58
+
* Scope: Definition of API extensions for I/O operations
59
+
* Meeting Schedule: Fortnightly on Thursdays at <ahref="https://time.is/1500_in_CT">3pm</a> US Central
* Scope: Ensure MPI has robust support for present and future language expressions and to introduce new language interfaces encapsulating the MPI concepts, currently focusing on modern C++.
65
+
* Note, this group will collaborate with the Fortran working group whenever helpful to advancing MPI.
66
+
* Meeting Schedule: Wednesdays at <ahref="https://time.is/0900_in_CT">9am</a> US Central Time
* Lead: Joseph Schuchart and Bill Gropp (prior lead: Rajeev Thakur)
71
+
* Scope: To re-examine the MPI RMA interface and consider additions and or changes needed to better support the one-sided programming model within MPI.
* Scope: Review and update semantic terms used throughout the MPI Standard.
93
+
94
+
#### Generalized Requests
95
+
96
+
* Scope: Redefine the generalized requests interface. A more flexible interface between the user defined requests and the MPI library is required in order to allow the provider of the generalized request to integrate a progress function inside the MPI library. The ultimate goal is to allow the generalized requests progress to be done without a special test or wait function.
97
+
98
+
#### [Point to Point Communication](https://github.com/mpiwg-p2p/p2p-issues/wiki)
99
+
100
+
* Scope: To re-examine the MPI peer communication semantics and interface, and consider additions and/or changes needed to better support point-to-point data movement within MPI.
* Scope: Work on definitions and specifications of operations that support higher performance forms of existing MPI operations when there is an ability to "plan once" and "amortize costs". Current work focuses on collective operations and neighborhood collectives.
0 commit comments