[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-devel] Question regarding calling tcp_output() from tcp_input(

From: Roy Shterman
Subject: Re: [lwip-devel] Question regarding calling tcp_output() from tcp_input() each time
Date: Wed, 9 Aug 2017 11:20:28 +0300

Thanks for the answer. helped a lot!

On 9 August 2017 at 00:00, address@hidden <address@hidden> wrote:
address@hidden wrote:
Of course that's not too good, but noone has provided a decent, working
solution for this, yet. Feel free to provide one :-)
One accepted improvement are "delayed ACKs" where we only send an empty
ACK for every 2nd segment.

Thinking about that, given an embedded OS which is strictly priority-driven, for netconn & sockets, maybe a solution would be to implement netconn_tcp_recvd to update an ACKed counter and send a message to tcpip_thread instead of using CORE_LOCK. That way, new segments arriving in tcpip_thread could send the updated window as piggy-back to the empty ACK...

This wouldn't change anything for callback API apps though.


lwip-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]