> Some memory leaks were solved in 1.4.5. that affects openib, see release
> notes.
Yes, with 1.4.4 was worse (it hanged in a previous part of the real code
with communications also involved) but with 1.4.5 it still hangs :( .
Now I see that in the first post there is another mistake :S , the
vers
At 16:19 09/05/2012, you wrote:
> On your code, the only point where it could fail is if one of the
> precalculated message size values is wrongly calculated and executes
> the Recieve where it shouldn't.
Yes, but after the sizes are calculated they don't change and that's why
I find it weird to
On Wed, 2012-05-09 at 15:24 +0200, Eduardo Morras wrote:
> Sorry for the delay, and sorry again because in last mail i had the
> wrong taste that it was some kind of homework problem.
Don't worry ;).
I simplified the core of the problem just to make it easier to
understand (at least that was my i
Sorry for the delay, and sorry again because in last mail i had the
wrong taste that it was some kind of homework problem.
At 17:41 04/05/2012, you wrote:
> The logic of send/recv looks ok. Now, in 5 and 7, recvSize(p2) and
> recvSize(p1) function what value returns?
All the sendSizes and Rec
On Fri, 2012-05-04 at 16:44 +0200, Eduardo Morras wrote:
> At 15:20 04/05/2012, you wrote:
> >Ups, I edited the code to make it easier to understand but I forgot
> >to change two p2, sorry ^^' .
> >I hope this one is completely right:
> >
> >1: for(int p1=0; p1 >2: for(int p2=0; p2 >3: if(me==p1)
At 15:20 04/05/2012, you wrote:
Ups, I edited the code to make it easier to understand but I forgot
to change two p2, sorry ^^' .
I hope this one is completely right:
1: for(int p1=0; p14: if(sendSize(p2))
MPI_Ssend(sendBuffer[p2],sendSize(p2),MPI_FLOAT,p2,0,myw);
//processor p1 sends data to
Ups, I edited the code to make it easier to understand but I forgot to
change two p2, sorry ^^' .
I hope this one is completely right:
1: for(int p1=0; p125) cout<<"p1("<25) cout<<"p1("<25) cout<<"p2("<25) cout<<"p2("< At 11:52 04/05/2012, you wrote:
> >Hi all,
> >
> >I have a program that execute
At 11:52 04/05/2012, you wrote:
Hi all,
I have a program that executes a communication loop similar to this one:
1:for(int p1=0; p14:if(sendSize(p2))
MPI_Ssend(sendBuffer[p2],sendSize(p2),MPI_FLOAT,p2,0,myw);
5:if(recvSize(p2))
MPI_Recv(recvBuffer[p2],recvS
Why? Removing the barrier will make all the other processors advance but
the processor that is waiting for the reception will wait forever.
Moreover, in the real code there is no Barrier. I use Isend's and
Irecv's and Wait's so I don't think that the problem is the Barrier.
I have tried to add "-m
Try removing the barrier.
On May 4, 2012, at 5:52 AM, Jorge Chiva Segura wrote:
> Hi all,
>
> I have a program that executes a communication loop similar to this one:
>
> 1:for(int p1=0; p1 2:for(int p2=0; p2 3:if(me==p1) {
> 4:if(sendSize(p2))
> MPI_Sse
Hi all,
I have a program that executes a communication loop similar to this one:
1:for(int p1=0; p1
11 matches
Mail list logo
