Difference between revisions of "PMI-2"

From Mpich
Jump to: navigation, search
m (Raffenet moved page Medusa to PMI-2)
m (Reverted edits by Raffenet (talk) to last revision by Gropp)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
[[Category:Design Documents]]
 
[[Category:Design Documents]]
For documentation related to the design of the Medusa PMI Library ([http://trac.mpich.org/projects/mpich/ticket/1034 tt#1034])
+
For the formal specification of PMI-2.
 +
 
 +
See [[PMI v2 API]] for some discussions about possible designs and some issues.
 +
 
 +
 
 +
== Design Requirements ==
 +
(WDG - I find it valuable to list objectives and requirements first. Here's an initial list. They can and should be expanded, and the consequences of each understood)
 +
* Scalable - Semantics of operations must permit scalable implementation
 +
* Efficient - Must provide MPI implementation with the information that it needs without requiring potentially expensive steps.
 +
* Complete - Must support all of MPI, including dynamic processes
 +
* Robust - Must handle failures and aborts, including any resources acquired by the MPI application.
 +
* Correct - Must avoid race conditions in the design
 +
* Portable - Must not assume a particular environment such as POSIX

Latest revision as of 21:01, 16 June 2014

For the formal specification of PMI-2.

See PMI v2 API for some discussions about possible designs and some issues.


Design Requirements

(WDG - I find it valuable to list objectives and requirements first. Here's an initial list. They can and should be expanded, and the consequences of each understood)

  • Scalable - Semantics of operations must permit scalable implementation
  • Efficient - Must provide MPI implementation with the information that it needs without requiring potentially expensive steps.
  • Complete - Must support all of MPI, including dynamic processes
  • Robust - Must handle failures and aborts, including any resources acquired by the MPI application.
  • Correct - Must avoid race conditions in the design
  • Portable - Must not assume a particular environment such as POSIX