[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] Possible deadlock in LWIP 1.3.1 RC1
From: |
Kieran Mansley |
Subject: |
Re: [lwip-users] Possible deadlock in LWIP 1.3.1 RC1 |
Date: |
Tue, 25 Aug 2009 10:31:53 +0100 |
On Tue, 2009-08-25 at 12:12 +0300, Eran Rundstein wrote:
> Regarding the first issue mentioned - I figured it has something to do
> with the fact my Python script sends data (100000 bytes at a time) and
> then only reads 10000.
> At some stage, I believe, the receive buffers on the machine running
> the Python script gets full and data starts getting queued on the LWIP
> side - does this make any sense?
Yes, I suppose it could just be that the send queue is full. I think
the socket would block in that case waiting for the other end to ACK
more of the data and free some space.
Kieran
- RE: [lwip-users] IP Address Display Functions, (continued)
- RE: [lwip-users] IP Address Display Functions, Kieran Mansley, 2009/08/25
- RE: [lwip-users] IP Address Display Functions, Kieran Mansley, 2009/08/25
- [lwip-users] Re: IP Address Display Functions, Jakob Stoklund Olesen, 2009/08/25
- RE: [lwip-users] Re: IP Address Display Functions, Bill Auerbach, 2009/08/25
- Re: [lwip-users] Re: IP Address Display Functions, address@hidden, 2009/08/25
- Re: [lwip-users] Re: IP Address Display Functions, address@hidden, 2009/08/25
- RE: [lwip-users] Re: IP Address Display Functions, Bill Auerbach, 2009/08/26
Re: [lwip-users] Possible deadlock in LWIP 1.3.1 RC1, Eran Rundstein, 2009/08/24
Re: [lwip-users] Possible deadlock in LWIP 1.3.1 RC1, address@hidden, 2009/08/24