From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: kuznet@ms2.inr.ac.ru
Cc: davem@redhat.com, ak@muc.de, linux-kernel@vger.kernel.org
Subject: Re: Excessive TCP retransmits over lossless, high latency link
Date: Mon, 3 Sep 2001 18:57:00 +0100 [thread overview]
Message-ID: <20010903185700.A12529@thefinal.cern.ch> (raw)
In-Reply-To: <20010901210212.A3361@thefinal.cern.ch> <200109031714.VAA24484@ms2.inr.ac.ru>
In-Reply-To: <200109031714.VAA24484@ms2.inr.ac.ru>; from kuznet@ms2.inr.ac.ru on Mon, Sep 03, 2001 at 09:14:47PM +0400
kuznet@ms2.inr.ac.ru wrote:
> > Yes, definitely. Btw, I saw a ping round trip time of 162s just now.
>
> I do not understand, do you share this link with someone or
> ping over tcp connection?
I was doing ping with the TCP connection going. When there is no TCP
connection, ping time is 1-1.5 seconds.
> > I saw very few retransmits in a single message download. SACK appears
> > occasionally. I don't really understand the local reaction to SACK, or
> > why a SACK option appears in one ACK sent locally and not the following
> > ACK, even though the SACK mentions data that does not arrive between the
> > two locally sent ACKs.
>
> But I do not see _any_ sacks in your tcpdumps.
Sorry, you are right. I did see an sack, but not in this trace.
> > The throughput difference was obvious: POP3 negotiation + 30k message +
> > headers took:
> >
> > 5 min 31 sec downloading unknown OS -> Linux 2.4.7
> > 2 min 15 sec downloading Linux 2.4.2 -> Linux 2.4.7
>
> It is dominated by rtt, one rtt per segment. It is very strange
> that cwnd does not want to open. Maybe, it is worth to tcpdump at proxy.
Do you mean that you want to see the Linux -> Linux connection, with
tcpdumps at both ends?
-- Jamie
next prev parent reply other threads:[~2001-09-03 17:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-01 17:17 Excessive TCP retransmits over lossless, high latency link Jamie Lokier
2001-09-01 17:41 ` Andi Kleen
2001-09-01 18:12 ` kuznet
2001-09-01 18:22 ` Jamie Lokier
2001-09-01 19:07 ` Neil Spring
2001-09-01 18:08 ` kuznet
2001-09-01 18:55 ` Jamie Lokier
2001-09-01 19:20 ` kuznet
2001-09-01 20:02 ` Jamie Lokier
2001-09-01 20:39 ` Lukas Beeler
2001-09-03 17:14 ` kuznet
2001-09-03 17:57 ` Jamie Lokier [this message]
2001-09-03 18:07 ` kuznet
2001-09-01 19:59 ` Alan Cox
[not found] <20010901195532.B2714@thefinal.cern.ch.suse.lists.linux.kernel>
[not found] ` <200109011920.XAA20031@ms2.inr.ac.ru.suse.lists.linux.kernel>
[not found] ` <20010901210212.A3361@thefinal.cern.ch.suse.lists.linux.kernel>
[not found] ` <20010901223918.A4053@mail.projectdream.org.suse.lists.linux.kernel>
2001-09-01 21:45 ` Andi Kleen
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=20010903185700.A12529@thefinal.cern.ch \
--to=lk@tantalophile.demon.co.uk \
--cc=ak@muc.de \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@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