dupack counter processing
hiren panchasara
hiren at strugglingcoder.info
Thu Nov 19 23:14:42 UTC 2015
+ freebsd-net as this deserves more eyeballs, imo.
On 10/17/15 at 05:37P, hiren panchasara wrote:
> On 10/07/15 at 12:17P, Randall Stewart via freebsd-transport wrote:
> >
> > 2) When we recognize a dup-ack we *will not* recognize it if for example if the rwnd changes even
> > if new SACK information is reported in the sack blocks. This is due to the fact that in non-SACK you don?t
> > (on purpose) recognize ACK?s where the window changed (since you can?t really tell if its a
> > plain window update or a dup-ack).. This means we occasionally miss out
> > on stroking the dup-ack counter and getting out of recovery....
After a lot of discussion with Randall and colleagues at Limelight, here
is the patch for review: https://reviews.freebsd.org/D4225
This changes the default behavior of how we detect loss. I'd appreciate
review/comments.
Cheers,
Hiren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 603 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-transport/attachments/20151119/4940224f/attachment.bin>
More information about the freebsd-transport
mailing list