From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Jones Subject: Re: TCP connection issues against Amazon S3 Date: Tue, 06 Jan 2015 11:48:21 -0800 Message-ID: <54AC3C05.1050704@hp.com> References: <5DCDADEF-FF9C-4844-8A2C-62E2D3B3B8CE@bengler.no> <1420560253.32621.20.camel@edumazet-glaptop2.roam.corp.google.com> <1420564837.32621.30.camel@edumazet-glaptop2.roam.corp.google.com> <8C4F7938-DCA1-46F5-A3C9-7DF62511DEE7@bengler.no> <54AC348B.4030900@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Eric Dumazet , "linux-kernel@vger.kernel.org" , netdev To: Yuchung Cheng , Erik Grinaker Return-path: In-Reply-To: <54AC348B.4030900@hp.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 01/06/2015 11:16 AM, Rick Jones wrote: > I'm assuming one incident starts at XX:41:24.748265 in the trace? That > does look like it is slowly slogging its way through a bunch of lost > traffic, which was I think part of the problem I was seeing with the > middlebox I stepped in, but I don't think I see the reset where I would > have expected it. Still, it looks like the sender has an increasing TCP > RTO as it is going through the slog (as it likely must since there are > no TCP timestamps?), to the point it gets larger than I'm guessing curl > was willing to wait, so the FIN at XX:41:53.269534 after a ten second or > so gap. Should the receiver's autotuning be advertising an ever larger window the way it is while going through the slog of lost traffic? rick