|
From: | Noam Weissman |
Subject: | Re: [lwip-users] Lwip tcp-stack reliability issue when using non-reliable network? |
Date: | Tue, 7 Nov 2017 16:21:58 +0000 |
Hi, So maybe enlarge
MEMP_NUM_PBUF
100-150 your have the memory for it J Noam. From: lwip-users [mailto:lwip-users-bounces+address@hidden
On Behalf Of Itzik Levi Hi Noam, Thanks. Just increased both MEMP_NUM_PBUF to 50, MEM_NUM_TCP_PCB TO 15. I'm not sure if its harder to reproduce(longer time to run) - maybe. but it still happens.. On Tue, Nov 7, 2017 at 5:36 PM, Noam Weissman <address@hidden> wrote: Hi, Check that you have MEMP_NUM_PBUF 50 or more
that MEMP_NUM_TCP_PCB is 15 or more The above may help, I think. Noam. From: lwip-users [mailto:lwip-users-bounces+noam=address@hidden]
On Behalf Of Itzik Levi Unfortunately, enabling Nagle did not do the trick, still got the same result. :( On Tue, Nov 7, 2017 at 4:20 PM, Itzik Levi <address@hidden> wrote: Thanks for the reply! Actually, the end goal is to integrate the solution into rfcomm. For now, the "physical layer" is being simulated by a single local host tcp connection(under Android OS). The losses are simulated by simply randomly dropping data in lwip's pppos "output_cb". I'll attempt to re-enable Nagle, see if there is any changes and report back. On Tue, Nov 7, 2017 at 4:09 PM, Gisle Vanem <address@hidden> wrote: Itzik Levi wrote: I'll go over your lwipopts and see whether I missed something.
|
[Prev in Thread] | Current Thread | [Next in Thread] |