Current issues problems under discussion

Current issues/problems under discussion

Different thread support level per session

May need a few more functions to be always thread safe. Can two different MPI libraries be loaded to handle this? Enum flags during session init or bool flag plus info key?

Getting names of sets to which you don't belong

Can this be permitted? Universal naming system? Policies controlling access? Private until explicitly published? FT implications?

Handling errors when there is no error handler

Applies to infos, ops, datatypes, errhandlers Probably make all these use errors return? Related to FT WG work on re-vamp of error handlers

Dynamic process sets and spawn/exec

Do we need an MPI_EXEC_REPLACE to re-use process resources? Naming for sets after MPI_EXEC, mpi://WORLD or not?

Impact on/from Tools?

Multiple thread support levels Multiple attached MPI libraries Handle introspection, shadow sessions or PMPI/QMPI

Impact on/from FT?

Handling errors when there is no error handler