diff options
| author |   David S. Miller <davem@davemloft.net> | 2019-01-17 15:12:26 -0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2019-01-17 15:12:26 -0800 |
| commit | 12ff91c8bac0b4650f6bb60c4477bd33bbe74b07 (patch) | |
| tree | 3b264a3fb495fd15153869e2b129a0d8cad4c944 /drivers/net/vxlan.c | |
| parent | net: phy: micrel: use phy_read_mmd and phy_write_mmd (diff) | |
| parent | tcp: less aggressive window probing on local congestion (diff) | |
| download | linux-dev-12ff91c8bac0b4650f6bb60c4477bd33bbe74b07.tar.xz linux-dev-12ff91c8bac0b4650f6bb60c4477bd33bbe74b07.zip | |
Merge branch 'improving-TCP-behavior-on-host-congestion'
Yuchung Cheng says:
====================
improving TCP behavior on host congestion
This patch set aims to improve how TCP handle local qdisc congestion
by simplifying the previous implementation. Previously when an
skb fails to (re)transmit due to local qdisc congestion or other
resource issue, TCP refrains from setting the skb timestamp or the
recovery starting time.
This design makes determining when to abort a stalling socket more
complicated, as the timestamps of these tranmission attempts were
missing. The stack needs to sort of infer when the original attempt
happens. A by-product is a socket may disregard the system timeout
limit (i.e. sysctl net.ipv4.tcp_retries2 or USER_TIMEOUT option),
and continue to retry until the transmission is successful.
In data-center environment when TCP RTO is small, this could cause
the socket to retry frequently for long during qdisc congestion.
The solution is to first unconditionally timestamp skb and recovery
attempt. Then retry more conservatively (twice a second) on local
qdisc congestion but abort the sockets according to the system limit.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/vxlan.c')
0 files changed, 0 insertions, 0 deletions