Thanks for the reply. I've somewhat figured it out the reason. It seems
that when a non-blocking send is posted, mpi doesn't spawn another process
that takes care the sending. The sending occurs only when the processor is
idle. Since the data I sent was immense (2) elements, there wasn't
su
I'll take a stab at this since I don't remember seeing any other
replies.
At least in the original code you sent out, you used Isend/sleep/Wait
to send messages. So, I'm guessing that part of the message is sent,
Iprobe detects that a matching message is in-coming, and then the
receiver goes
This email contained a .zip file attachment. Raytheon does not allow email
attachments that are considered likely to contain malicious code. For your
protection this attachment has been removed.
If this email is from an unknown source, please simply delete this email.
If this email was expected
I have modified the code so that all the terminal outputs are done by one
executable. I have attached the source files, after compiling type "make
go" and the code will execute.
The previous code output was from a supercomputer cluster where the two
processes resides on two different nodes. When
On Sat, Jun 5, 2010 at 2:44 PM, David Zhang wrote:
> Dear all:
>
> I'm using mpi_iprobe to serve as a way to send signals between different
> mpi executables. I'm using the following test codes (fortran):
>
> #1
> program send
> implicit none
> include 'mpif.h'
>
> real*8 :: vec(2)=1.
