From: Eric Dumazet <eric.dumazet@gmail.com>
To: Yuchung Cheng <ycheng@google.com>
Cc: "Esztermann, Ansgar" <Ansgar.Esztermann@mpi-bpc.mpg.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: TCP fast retransmit
Date: Wed, 14 Dec 2011 23:31:49 +0100 [thread overview]
Message-ID: <1323901909.2631.17.camel@edumazet-laptop> (raw)
In-Reply-To: <CAK6E8=dcG3mw8r4FXt62G-0uoRNa9tcyQL3DS62MYe8F=9R6Nw@mail.gmail.com>
Le mercredi 14 décembre 2011 à 11:00 -0800, Yuchung Cheng a écrit :
> >
> I use tcptrace to check the time sequence and I am puzzled:
> I see a lot of OOO packets too but how can this happen at a sender-side trace?
> unless the trace is taken close to but not exactly at the sender.
> I expect on seeing in-sequence packets but a lots of SACKs plus some
> spurious retransmists.
I understood the trace was a receiver-side one (a linux machine if I am
not mistaken, while the sender is AIX powered)
(Looking at timings of ACKS, coming a few us after corresponding data
packet arrival)
next prev parent reply other threads:[~2011-12-14 22:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 13:33 TCP fast retransmit Esztermann, Ansgar
2011-11-25 16:36 ` Eric Dumazet
2011-11-25 16:39 ` Eric Dumazet
2011-11-29 9:00 ` Esztermann, Ansgar
2011-12-09 13:34 ` Esztermann, Ansgar
2011-12-09 14:43 ` Eric Dumazet
2011-12-09 16:17 ` Esztermann, Ansgar
2011-12-09 16:31 ` Eric Dumazet
2011-12-13 14:05 ` Esztermann, Ansgar
2011-12-13 14:31 ` Eric Dumazet
2011-12-13 14:59 ` Carsten Wolff
2011-12-14 19:00 ` Yuchung Cheng
2011-12-14 22:31 ` Eric Dumazet [this message]
2011-12-15 7:41 ` Carsten Wolff
2011-12-15 8:24 ` Eric Dumazet
2011-12-16 15:53 ` Esztermann, Ansgar
2011-11-25 16:57 ` Ilpo Järvinen
2011-11-28 21:17 ` Yuchung Cheng
2011-11-29 9:00 ` Esztermann, Ansgar
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=1323901909.2631.17.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=Ansgar.Esztermann@mpi-bpc.mpg.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox