Re: [lwip-users] bug&patch: when an api_msg is lost tcp get stuck

[Leon Woestenberg]

Hello all,

Renzo Davoli wrote:

> When I received heavy bursty data (10MB per burst) using TCP in LwIP
> everything blocked.
>
> The problem appears to be the following one:
> when an api_msg gets lost (no more available elements in memp)
> the window is not updated through tcp_recved (called by do_recv in api_msg.c).
>
> Thus the tcp window reaches zero size and everything is blocked.
>  

Interesting. How can we cope with this in a more generic matter - i.e. 
outside the wrapper API, but inside
the core API (tcp.c, tcp_in.c, tcp_out.c) instead?

Should we try to open up the window? How do other stacks with zeroed 
windows?

Regards,

Leon.