[Top][All Lists]

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

[lwip-devel] [task #14128] Appropriate byte counting/stretch ACK support

From: Joel Cunningham
Subject: [lwip-devel] [task #14128] Appropriate byte counting/stretch ACK support
Date: Wed, 19 Apr 2017 12:42:09 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.1 Safari/603.1.30

Follow-up Comment #23, task #14128 (project lwip):

 > Looks good, too. The downside is that this is another option noone will
ever change. Since the default is 'enabled', maybe it's better to just use it
and dump the old behaviour? All the #if code looks so ugly... 

I'm fine with removing the old behavior, which would mean we don't need an
LWIP_TCB_ABC option. I suppose I was just being conservative about the changes

> Oh, and regarding comment #16: how much sense does it make to configure the
limit if we only allow integers? The only possible settings seem to be '1' or
'2', reading the RFC.

Someone being more experimental could set the LIMIT to a higher value than 2
to support stretch ACKs spanning more than 2 segments, even though that's
against the RFC's guidance.  Maybe having this as an option is
over-thinking/engineering it.  We could just use 2 for now and then revisit it
as an option if there is desire/feedback from users.  What do you think?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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