g message
is." But even if that proposal passes, it'll likely be a while before
it shows up in MPI implementations. :-\
On Jun 4, 2009, at 10:27 AM, Neil Ludban wrote:
> Date: Thu, 4 Jun 2009 11:14:16 +1000
> From: Lars Andersson
> Subject: [OMPI users] Receiving MPI me
> Date: Thu, 4 Jun 2009 11:14:16 +1000
> From: Lars Andersson
> Subject: [OMPI users] Receiving MPI messages of unknown size
> To: us...@open-mpi.org
>
> When using blocking message passing, I have simply solved the problem
> by first sending a small, fixed size header c
> On Thu, 2009-06-04 at 14:54 +1000, Lars Andersson wrote:
>> Hi Gus,
>>
>> Thanks for the suggestion. I've been thinking along those lines, but
>> it seems to have drawbacks. Consider the following MPI conversation:
>>
>> Time NODE 1 NODE 2
>> 0 local work local work
On Thu, 2009-06-04 at 14:54 +1000, Lars Andersson wrote:
> Hi Gus,
>
> Thanks for the suggestion. I've been thinking along those lines, but
> it seems to have drawbacks. Consider the following MPI conversation:
>
> TimeNODE 1 NODE 2
> 0local work
On Thu, Jun 4, 2009 at 2:54 PM, Lars Andersson wrote:
> Hi Gus,
>
> Thanks for the suggestion. I've been thinking along those lines, but
> it seems to have drawbacks. Consider the following MPI conversation:
>
> Time NODE 1 NODE 2
> 0 local work
Hi Gus,
Thanks for the suggestion. I've been thinking along those lines, but
it seems to have drawbacks. Consider the following MPI conversation:
TimeNODE 1 NODE 2
0local work local work
1post n-b recv
Hi Lars
I wonder if you could always use blocking message passing on the
preliminary send/receive pair that transmits the message size/header,
then use non-blocking mode for the actual message.
If the "message size/header" part transmits a small buffer,
the preliminary send/recv pair will use t
Hi,
I'm trying to solve a problem of passing serializable, arbitrarily
sized objects around using MPI and non-blocking communication. The
problem I'm facing is what to do at the receiving end when expecting
an object of unknown size, but at the same time not block on waiting
for it.
When using bl
