[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] Question regarding calling tcp_output() from tcp_input(
Re: [lwip-devel] Question regarding calling tcp_output() from tcp_input() each time
Tue, 8 Aug 2017 23:00:10 +0200
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
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.