Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] mca_pml_ob1_send blocks
From: Shaun Jackman (sjackman_at_[hidden])
Date: 2009-08-25 18:51:41

Jeff Squyres wrote:
> On Aug 24, 2009, at 2:18 PM, Shaun Jackman wrote:
>> I'm seeing MPI_Send block in mca_pml_ob1_send. The packet is shorter
>> than the eager transmit limit for shared memory (3300 bytes < 4096
>> bytes). I'm trying to determine if MPI_Send is blocking due to a
>> deadlock. Will MPI_Send block even when sending a packet eagerly?
> It can, yes. Message size is one of multiple factors that can cause
> MPI_SEND to block -- so yes, it's even possible for short/eager
> messages to block in MPI_SEND.
> Can you tell if the corresponding receive has already been posted and
> is making progress in the receiver?

Hi Jeff,

The receiver posts a single MPI_Irecv in advance, and as soon as it's
received a message it posts a new MPI_Irecv. However, there are
multiple processes sending to the receiver, and only one MPI_Irecv posted.