git://ftp.safe.ca / safe / jmp / linux-2.6 / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 66e93e4) | patch
[TCP]: Prevent reordering adjustments during FRTO
authorIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
Thu, 22 Feb 2007 07:14:42 +0000 (23:14 -0800)
committerDavid S. Miller <davem@sunset.davemloft.net>
Thu, 26 Apr 2007 05:23:15 +0000 (22:23 -0700)
commit288035f915686a9a9e85e0358c5392bb5d7ae58d
treefcf6684a8750e12f5bb9d3a7f70062a574b3ff03tree | snapshot
parent66e93e45c09affa407750cc06398492e8b897848commit | diff
[TCP]: Prevent reordering adjustments during FRTO

To be honest, I'm not too sure how the reord stuff works in the
first place but this seems necessary.

When FRTO has been active, the one and only retransmission could
be unnecessary but the state and sending order might not be what
the sacktag code expects it to be (to work correctly).

Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/tcp_input.c diff | blob | history
Full containers within linux kernel