LAM/MPI Development Mailing List Archives

From: Samuel RICHARD (samuel.richard_at_[hidden])
Date: 2006-01-18 19:09:28

• Next message: Jeff Squyres: "Re: TCP rpi behaviour when tcp send buffer is full"
• Previous message: Jeff Squyres: "Re: lam-devel Digest, Vol 141, Issue 1"
• Next in thread: Jeff Squyres: "Re: TCP rpi behaviour when tcp send buffer is full"
• Reply: Jeff Squyres: "Re: TCP rpi behaviour when tcp send buffer is full"

Hi,

I was wondering what happens with LAM MPI tcp rpi if the TCP send buffer
(inside the kernel) is full (the application is computing faster than the
network sends packets).
I think the socket API must return an error when the application is trying
to write data to the socket but how does LAM behaves in such a case?
Does LAM tries to re-send data after a defined delay?

Thanks for any help.

• Next message: Jeff Squyres: "Re: TCP rpi behaviour when tcp send buffer is full"
• Previous message: Jeff Squyres: "Re: lam-devel Digest, Vol 141, Issue 1"
• Next in thread: Jeff Squyres: "Re: TCP rpi behaviour when tcp send buffer is full"
• Reply: Jeff Squyres: "Re: TCP rpi behaviour when tcp send buffer is full"