|
From: | Itzik Levi |
Subject: | Re: [lwip-users] Lwip tcp-stack reliability issue when using non-reliable network? |
Date: | Tue, 7 Nov 2017 17:29:14 +0200 |
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.
In addition, I will attempt to useSO_SNDTIMEO and SO_RCVTIMEO instead of polling in parallel to write and read(I understand by the samples its a more health way of using this api).
If you have anymore suggestions, that will be great!
I think you wrote earlier than you had disabled
"Nagle algorithm". Are you sure that's a good idea?
Maybe you're saturating your RF-link with small fragments.
Just a thought since it's almost never a good idea to
turn off Nagle.
--
--gv
_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users
[Prev in Thread] | Current Thread | [Next in Thread] |