Re: [RFC PATCH RESEND] tcp: avoid F-RTO if SACK and timestamps are disabled
From: Eric Dumazet
Date: Wed Jun 13 2018 - 13:48:13 EST
On 06/13/2018 10:32 AM, Yuchung Cheng wrote:
> On Wed, Jun 13, 2018 at 9:55 AM, Michal Kubecek <mkubecek@xxxxxxx> wrote:
>> When F-RTO algorithm (RFC 5682) is used on connection without both SACK and
>> timestamps (either because of (mis)configuration or because the other
>> endpoint does not advertise them), specific pattern loss can make RTO grow
>> exponentially until the sender is only able to send one packet per two
>> minutes (TCP_RTO_MAX).
>> Signed-off-by: Michal Kubecek <mkubecek@xxxxxxx>
> Acked-by: Yuchung Cheng <ycheng@xxxxxxxxxx>
> Thanks for the patch (and packedrill test)!
Yes, thanks a lot Michal.
Signed-off-by: Eric Dumazet <edumazet@xxxxxxxxxx>