Re: [PATCH net-next v3] tcp: use RFC6298 compliant TCP RTO calculation

2016-06-29 Thread Daniel Metz
BD R Y -- mean TCPRecovLat 3s -7% +39% +38% mean TCPRecovLat252s +1% -11% -11% This is indeed very interesting and somewhat unexpected. Do

Re: [PATCH net-next v2] tcp: use RFC6298 compliant TCP RTO calculation

2016-06-15 Thread Daniel Metz
Yuchung Cheng | 2016-06-15 20:02: > Let me explain in a different way: > > * RFC6298 applies a lower bound of 1 second to RTO (section 2.4) > > * Linux currently applies a lower bound of 200ms (min_rto) to > K*RTTVAR, but /not/ RTO itself. > > * This patch applies the lower bound of 200ms to RTO,

[PATCH net-next v3] tcp: use RFC6298 compliant TCP RTO calculation

2016-06-15 Thread Daniel Metz
From: Daniel Metz <daniel.m...@rohde-schwarz.com> This patch adjusts Linux RTO calculation to be RFC6298 Standard compliant. MinRTO is no longer added to the computed RTO, RTO damping and overestimation are decreased. In RFC 6298 Standard TCP Retransmission Timeout (RTO) calcu

[PATCH net-next v2] tcp: use RFC6298 compliant TCP RTO calculation

2016-06-14 Thread Daniel Metz
From: Daniel Metz <daniel.m...@rohde-schwarz.com> This patch adjusts Linux RTO calculation to be RFC6298 Standard compliant. MinRTO is no longer added to the computed RTO, RTO damping and overestimation are decreased. In RFC 6298 Standard TCP Retransmission Timeout (RTO) calcu

[PATCH net-next] tcp: use RFC6298 compliant TCP RTO calculation

2016-06-13 Thread Daniel Metz
/1pKmPfnQb6fDK4qpiNVkN8cQyGE4wYDZukcuZfR-BnnM/ Signed-off-by: Hagen Paul Pfeifer <ha...@jauu.net> Signed-off-by: Daniel Metz <dm...@mytum.de> Cc: Eric Dumazet <eduma...@google.com> Cc: Yuchung Cheng <ych...@google.com> Cc: Neal Cardwell <ncardw...@google.com> --- We removed outdated com