summaryrefslogtreecommitdiffstats
path: root/drivers/block/ps3vram.c
diff options
context:
space:
mode:
authorYuchung Cheng <ycheng@google.com>2014-08-22 23:15:22 +0200
committerDavid S. Miller <davem@davemloft.net>2014-08-23 06:28:02 +0200
commit989e04c5bc3ff77d65e1f0d87bf7904dfa30d41c (patch)
treef9e12506a3e88dd1a74088d2137c4126108d5efd /drivers/block/ps3vram.c
parentphylib: use MDIO_DEVS[12] (diff)
downloadlinux-989e04c5bc3ff77d65e1f0d87bf7904dfa30d41c.tar.xz
linux-989e04c5bc3ff77d65e1f0d87bf7904dfa30d41c.zip
tcp: improve undo on timeout
Upon timeout, undo (via both timestamps/Eifel and DSACKs) was disabled if any retransmits were still in flight. The concern was perhaps that spurious retransmission sent in a previous recovery episode may trigger DSACKs to falsely undo the current recovery. However, this inadvertently misses undo opportunities (using either TCP timestamps or DSACKs) when timeout occurs during a loss episode, i.e. recurring timeouts or timeout during fast recovery. In these cases some retransmissions will be in flight but we should allow undo. Furthermore, we should only reset undo_marker and undo_retrans upon timeout if we are starting a new recovery episode. Finally, when we do reset our undo state, we now do so in a manner similar to tcp_enter_recovery(), so that we require a DSACK for each of the outstsanding retransmissions. This will achieve the original goal by requiring that we receive the same number of DSACKs as retransmissions. This patch increases the undo events by 50% on Google servers. Signed-off-by: Yuchung Cheng <ycheng@google.com> Signed-off-by: Neal Cardwell <ncardwell@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/block/ps3vram.c')
0 files changed, 0 insertions, 0 deletions