I knew someone was going to ask :) Mike asked me to add 2pm EST to the times listed. Can you guys go and update those boxes? It looks like Thursday 2pm EST is our best shot at convergence.
-----Original Message----- From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain Sent: Tuesday, October 29, 2013 1:58 PM To: Open MPI Developers Subject: Re: [OMPI devel] CM PML / OpenSHMEM Did that time get finalized? I recall the doodle, but not seeing a final decision On Oct 29, 2013, at 10:53 AM, Joshua Ladd <josh...@mellanox.com> wrote: > These (and others) are exactly the issues we need to discuss with you guys > next week. > > Josh > > -----Original Message----- > From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph > Castain > Sent: Tuesday, October 29, 2013 1:29 PM > To: Open MPI Developers > Subject: Re: [OMPI devel] CM PML / OpenSHMEM > > I think the issue that may have caused this was the need for a double modex > if the MPI layer selected a PML that used an MTL, and then the user provided > oshmem MCA params specifying they use the BTL-related SPML component. My > guess is that the defaults wound up creating that situation, which then led > to the clean abort. > > Probably just a question of correctly setting defaults in the CM scenario. > > On Oct 29, 2013, at 10:02 AM, Barrett, Brian W <bwba...@sandia.gov> wrote: > >> Mellanox - >> >> It looks like someone fixed the segfault when calling start_pes() >> when the CM PML is in use. However, I'm not sure that a clean abort >> is much better. With the proc tags code (in both the trunk and >> v1.7), there's no reason that you can't initialize both the btls and mtls. >> This may require some additional coding, but I think it should be >> doable. I'm happy to help with advice / discuss implementation >> issues, but not supporting OpenSHMEM when the CM PML is in use is >> unacceptable and is, in my mind, a blocker for v1.7. >> >> Brian >> >> -- >> Brian W. Barrett >> Scalable System Software Group >> Sandia National Laboratories >> >> >> >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/devel > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel _______________________________________________ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel
