Hi Jeff, checkpoint/restart is not supported in this release.
Does this release work with totalview? I recall we had some problems, and do not remember if they were resolved. We may also want to clarify if any PML/MTLs are experimental in this release. MPI_THREAD_MULTIPLE support. Howard 2016-04-29 10:34 GMT-06:00 Cabral, Matias A <matias.a.cab...@intel.com>: > How about for “developers that have not been following the transition from > 1.x to 2.0? Particularly myself J. I started contributing to some > specific parts (psm2 mtl) and following changes. However, I don’t have > details of what is changing in 2.0. I see there could be different level of > details in the “developer’s transition guide book”, ranging from > architectural change to what pieces were moved where. > > > > Thanks, > > > > _MAC > > > > *From:* devel [mailto:devel-boun...@open-mpi.org] *On Behalf Of *Joshua > Ladd > *Sent:* Friday, April 29, 2016 7:11 AM > *To:* Open MPI Developers <de...@open-mpi.org> > *Subject:* Re: [OMPI devel] 2.0.0 is coming: what do we need to > communicate to users? > > > > Certainly we need to communicate / advertise / evangelize the improvements > in job launch - the largest and most substantial change between the two > branches - and provide some best practice guidelines for usage (use direct > modex for applications with sparse communication patterns and full modex > for dense.) I would be happy to contribute some paragraphs. > > > > Obviously, we also need to communicate, reiterate the need to recompile > codes built against the 1.10 series. > > > > Best, > > > > Josh > > > > > > On Thursday, April 28, 2016, Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > > We're getting darn close to v2.0.0. > > What "gotchas" do we need to communicate to users? I.e., what will people > upgrading from v1.8.x/v1.10.x be surprised by? > > The most obvious one I can think of is mpirun requiring -np when slots are > not specified somehow. > > What else do we need to communicate? It would be nice to avoid the > confusion users experienced regarding affinity functionality/options when > upgrading from v1.6 -> v1.8 (because we didn't communicate these changes > well, IMHO). > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/04/18832.php > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/04/18843.php >
