Thanks Dick, Eugene. That's what I figured. I was just hoping there might
be some more obscure MPI functions that might do what I want. I'll go ahead
and write my own yielding wrapper on irecv.
Thanks again,
Brian
sent from mobile phone
On Oct 20, 2010 5:24 AM, "Richard Treumann" wrote:
Brian
Most HPC applications are run with one processor and one working thread
per MPI process. In this case, the node is not being used for other work
so if the MPI process does release a processor, there is nothing else
important for it to do anyway.
In these applications, the blocking MPI c
Brian Budge wrote:
Hi all -
I just ran a small test to find out the overhead of an MPI_Recv call
when no communication is occurring. It seems quite high. I noticed
during my google excursions that openmpi does busy waiting. I also
noticed that the option to -mca mpi_yield_when_idle seems no
