Re: [OMPI devel] This list is suspended while migrating

2016-07-27 Thread Jeff Squyres (jsquyres)
...and we're back. NOTE: the email address for this list has now changed! It is now @lists.open-mpi.org (it used to be @open-mpi.org). PLEASE UPDATE YOUR CONTACTS AND MAIL CLIENT FILTERS! > On Jul 27, 2016, at 12:01 PM, Jeff Squyres (jsquyres) > wrote: > > We are beginning the list mi

[OMPI devel] Mailing list migration: status

2016-07-27 Thread Jeff Squyres (jsquyres)
We have transitioned the Open MPI mailing lists to our new best friends at the New Mexico Consortium (http://newmexicoconsortium.org/). Thank you, NMC! For at least a little while, you'll see newmexicoconsortium.org in the footers of our mailing list mails. Eventually, we hope to replace those

Re: [OMPI devel] Mailing list migration: status

2016-07-27 Thread Jeff Squyres (jsquyres)
On Jul 27, 2016, at 2:20 PM, Jeff Squyres (jsquyres) wrote: > > 1. New mails will start showing up there as they are sent across the lists. > For example, the Open MPI "devel" list will show up under Argh: that should have read: For example, the Open MPI "devel" list will show up under http

Re: [OMPI devel] Performance analysis proposal

2016-07-27 Thread Sreenidhi Bharathkar Ramesh via devel
Hi Jeff, >> 1. How about evaluating FUNNELED and SERIALIZED performance ? > > For Open MPI, it's basically THREAD_MULTIPLE and not-THREAD_MULTIPLE. I.e., > there's no real difference between SINGLE, SERIALIZED, FUNNELED We were assuming that there would be cost due to locking/synchronization in