#1395 Deprecate MPI 1 in Dune 2.3 and state that the next release will require MPI 2.1
Metadata
Property | Value |
---|---|
Reported by | Steffen Müthing (steffen.muething@iwr.uni-heidelberg.de) |
Reported at | Dec 4, 2013 14:26 |
Type | Discussion |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Last edited by | Steffen Müthing (steffen.muething@iwr.uni-heidelberg.de) |
Last edited at | Dec 11, 2013 13:39 |
Closed by | Steffen Müthing (steffen.muething@iwr.uni-heidelberg.de) |
Closed at | Dec 11, 2013 13:39 |
Closed in version | 2.3 |
Resolution | Implemented |
Comment | Decided to go ahead with the deprecation in 2.3 after developer vote and added deprecation warning in dune-common ac6885f8a. |
Description
Some time ago, I asked around whether there are still any users of an MPI implementation that is not compatible with MPI 2.1 (basically, an MPI that was released before 2009) [1]
I didn't receive any answers at that time, so I propose to state that MPI-1.2 is deprecated in the release notes of Dune 2.3 and that for the next release after 2.3, an implementation compatible with MPI-2.1 will be required.
I am aware that it is already rather late in the release cycle, but I think the user impact would be minimal (all versions of MPICH 2+, MVAPICH 2+ and OpenMPI support MPI-2.1). Getting rid of MPI-1 would take care of some #ifdefs we currently have in the MPIHelper and - more importantly - would allow us to rely on the presence of MPI_Init_thread() and support for checking whether MPI was already initialized / finalized by an external library (important for things like PETSc).
I've added a doodle for the DUNE developers at http://users.dune-project.org/doodles/10
[1] http://lists.dune-project.org/pipermail/dune/2013-October/012496.html