[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #34517] persist timer is started although there is una
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #34517] persist timer is started although there is unacked data |
Date: |
Mon, 10 Oct 2011 09:04:35 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 |
Follow-up Comment #2, bug #34517 (project lwip):
We have implemented both: if tehre is already-sent (unacked) data, we send
that. If not, we send 1 out-of-window byte.
However, aside from the bug I just fixed (wrong byte was sent), I think that
if we have unacked data, we should send that whole segment instead of creating
a new segment and sending only one byte from it. From reading about TCP
implementations, it seems to be a common thing to combine RTO with persist
timer (which is roughly what my change would be - although still using 2
counter variables and the persist timer would still fire before the RTO timer
does).
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?34517>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/