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: Sat, 1 Sep 2001 19:55:32 +0100 [thread overview]
Message-ID: <20010901195532.B2714@thefinal.cern.ch> (raw)
In-Reply-To: <20010901181729.A2204@thefinal.cern.ch> <200109011808.WAA19782@ms2.inr.ac.ru>
In-Reply-To: <200109011808.WAA19782@ms2.inr.ac.ru>; from kuznet@ms2.inr.ac.ru on Sat, Sep 01, 2001 at 10:08:24PM +0400
kuznet@ms2.inr.ac.ru wrote:
> > The interesting thing is that there isn't any evidence of packet loss.
>
> Why did you disable bith sacks and timestamps? Exactly to get
> maximal damage from long delay link?
>
> What OS is sender? If it is linux too, try to use default configuration
> not playing with /proc/sys/net/tcp_*, especially with timestamps
> and sacks and the situation should rectify.
Unfortunately the other machine is my ISP, who I do not control. I have
no idea what the sender OS is, but it's obviously not a standard recent
Linux judging from the lack of SACK.
> Also, please, send full (binary!) tcpdump from SYN and to FIN.
I have send myself a 30k mail and produced a trace of receiving it. A
binary trace with "tcpdump -n -w" is attached, and a text version of it
with "tcpdump -r pktlog2" is appended below.
> Well, and if sender is not linux... no ideas.
I am wondering if not sending so many duplicate ACKs would help the
broken sender (I know, that is against RFC793 but hey if it works...).
For the sake of a Linux test, I shall try proxying this stream via a
Linux 2.4.2 box I have on the net, and see if it is an improvement.
-- Jamie
next prev parent reply other threads:[~2001-09-01 19:01 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 [this message]
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
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=20010901195532.B2714@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 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.