All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Yuchung Cheng <ycheng@google.com>, Erik Grinaker <erik@bengler.no>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: TCP connection issues against Amazon S3
Date: Tue, 06 Jan 2015 11:48:21 -0800	[thread overview]
Message-ID: <54AC3C05.1050704@hp.com> (raw)
In-Reply-To: <54AC348B.4030900@hp.com>

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

  reply	other threads:[~2015-01-06 19:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 15:14 TCP connection issues against Amazon S3 Erik Grinaker
2015-01-06 16:04 ` Eric Dumazet
2015-01-06 16:11   ` Erik Grinaker
2015-01-06 17:20     ` Eric Dumazet
2015-01-06 18:17       ` Erik Grinaker
2015-01-06 18:32         ` Eric Dumazet
2015-01-06 18:33         ` Yuchung Cheng
2015-01-06 19:01           ` Erik Grinaker
2015-01-06 19:18             ` Yuchung Cheng
2015-01-06 19:42               ` Erik Grinaker
2015-01-06 20:13                 ` Eric Dumazet
2015-01-06 20:26                   ` Erik Grinaker
2015-01-06 21:04                     ` Erik Grinaker
2015-01-06 22:00                       ` Yuchung Cheng
2015-01-07 13:31                         ` Erik Grinaker
2015-01-07 15:58                           ` Eric Dumazet
2015-01-07 20:37                             ` Erik Grinaker
2015-01-07 20:37                               ` Erik Grinaker
2015-01-07 21:33                               ` Eric Dumazet
2015-01-08 17:47                                 ` Erik Grinaker
2015-01-08 18:15                                   ` Eric Dumazet
2015-01-08 18:52                                     ` Rick Jones
2015-01-08 18:52                                       ` Rick Jones
2015-01-07 21:33                               ` Yuchung Cheng
2015-01-07  1:23                       ` Lukas Tribus
2015-01-07  1:23                         ` Lukas Tribus
2015-01-07 13:06                         ` Erik Grinaker
2015-01-06 19:16           ` Rick Jones
2015-01-06 19:48             ` Rick Jones [this message]
2015-01-06 19:50             ` Erik Grinaker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54AC3C05.1050704@hp.com \
    --to=rick.jones2@hp.com \
    --cc=eric.dumazet@gmail.com \
    --cc=erik@bengler.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ycheng@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.