Re: [lwip-devel] application above lwip too low - lwip memp overflow

[Piero 74]

i'm using socket...
i didn't free packets directly... my application only calls socket api.

2009/1/15 Mike Kleshov <address@hidden>

You'll be able to receive new packets when you free some of the pbufs
allocated for previous packets. This seems natural to me.
Why are you not able to recover from this?

- mike

2009/1/14 Piero 74 <address@hidden>:

> Hi all
>
> I'm testing performance of my lwip-application. I'm using socket (using
> select in a loop and recv) [lwip release: 1.3.0 stable]
>
> I found a strange problem:
>
> if i will send to my board packets very fast, after sompe packet i will have
> all pbuf of pool in use, and driver will not be able to add new packet.
> But in this situation, i cannot recovery the stack...
> my application after a timeout without packets closes the socket, but there
> is no way to free allcated pbufs
> (see attachment)
>
> there is something in the lwip head that can avoid this problem?
>
> Thanks
> Piero
>
>
>
>

> _______________________________________________
> lwip-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-devel
>
>


_______________________________________________
lwip-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-devel