Re: [OMPI devel] Change in OPAL / OMPI DPM system time during MPI_INIT

2010-11-22 Thread David Singleton
On 11/23/2010 06:47 AM, Barrett, Brian W wrote: Short answer: we need the "extra" decrement at the end of MPI init. Long answer: Ok, so I was somewhat wrong :). (surprised this didn't show up in testing). Confirmed with our basic pingpong test: vayu2:~/MPI > mpirun -n 2 ./pp142 | head -

Re: [OMPI devel] Change in OPAL / OMPI DPM system time during MPI_INIT

2010-11-22 Thread Barrett, Brian W
Short answer: we need the "extra" decrement at the end of MPI init. Long answer: Ok, so I was somewhat wrong :). The count of users is initialized to 0. If it's greater than zero, the event library is polled every time opal_progress() is called, which kills latency (surprised this didn't show

Re: [OMPI devel] Change in OPAL / OMPI DPM system time during MPI_INIT

2010-11-22 Thread Jeff Squyres
On Nov 22, 2010, at 11:35 AM, Barrett, Brian W wrote: > Um, the counter starts initialized at one. Does that mean that we should or should not leave that extra _decrement() in there? > Brian > > On Nov 22, 2010, at 9:32 AM, Jeff Squyres wrote: > >> A user noticed a specific change that we mad

Re: [OMPI devel] Change in OPAL / OMPI DPM system time during MPI_INIT

2010-11-22 Thread Barrett, Brian W
Um, the counter starts initialized at one. Brian On Nov 22, 2010, at 9:32 AM, Jeff Squyres wrote: > A user noticed a specific change that we made between 1.4.2 and 1.4.3: > >https://svn.open-mpi.org/trac/ompi/changeset/23448 > > which is from CMR https://svn.open-mpi.org/trac/ompi/ticket/2