From: Willy Tarreau <w@1wt.eu>
To: Klavs Klavsen <kl@vsen.dk>
Cc: Eric Dumazet <eric.dumazet@gmail.com>, netdev@vger.kernel.org
Subject: Re: TCP fast retransmit issues
Date: Wed, 26 Jul 2017 16:38:27 +0200 [thread overview]
Message-ID: <20170726143827.GD1737@1wt.eu> (raw)
In-Reply-To: <0b60368890bdb9aa1cf1df4bd0bf21cf@vsen.dk>
On Wed, Jul 26, 2017 at 04:25:29PM +0200, Klavs Klavsen wrote:
> Thank you very much guys for your insight.. its highly appreciated.
>
> Next up for me, is waiting till the network guys come back from summer
> vacation, and convince them to sniff on the devices in between to pinpoint
> the culprit :)
That said, Eric, I'm a bit surprized that it completely stalls. Shouldn't
the sender end up retransmitting unacked segments after seeing a certain
number of ACKs not making progress ? Or maybe this is disabled when SACKs
are in use but it seems to me that once invalid SACKs are ignored we should
ideally fall back to the normal way to deal with losses. Here the server
ACKed 3903858556 for the first time at 15:59:54.292743 and repeated this
one 850 times till 16:01:17.296407 but the client kept sending past this
point probably due to a huge window, so this looks suboptimal to me.
Willy
next prev parent reply other threads:[~2017-07-26 14:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 11:07 TCP fast retransmit issues Klavs Klavsen
2017-07-26 11:49 ` Eric Dumazet
2017-07-26 12:18 ` Klavs Klavsen
2017-07-26 13:31 ` Eric Dumazet
2017-07-26 13:42 ` Willy Tarreau
2017-07-26 14:32 ` Eric Dumazet
2017-07-26 14:50 ` Willy Tarreau
2017-07-26 16:43 ` Neal Cardwell
2017-07-26 17:06 ` Neal Cardwell
2017-07-26 18:38 ` Neal Cardwell
2017-07-26 19:02 ` Neal Cardwell
2017-07-28 22:54 ` Neal Cardwell
2017-08-01 3:17 ` Neal Cardwell
2017-07-28 6:53 ` Christoph Paasch
2017-07-26 14:08 ` Klavs Klavsen
2017-07-26 14:18 ` Willy Tarreau
2017-07-26 14:25 ` Klavs Klavsen
2017-07-26 14:38 ` Willy Tarreau [this message]
2017-07-28 6:36 ` Klavs Klavsen
2017-07-28 7:27 ` Willy Tarreau
2017-08-17 13:20 ` Jeremy Harris
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=20170726143827.GD1737@1wt.eu \
--to=w@1wt.eu \
--cc=eric.dumazet@gmail.com \
--cc=kl@vsen.dk \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).