From: Mika Liljeberg <Mika.Liljeberg@welho.com>
To: Hayden Myers <hayden@spinbox.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: 2.2 to 2.4... serious TCP send slowdowns
Date: 22 Jul 2002 22:51:27 +0300 [thread overview]
Message-ID: <1027367487.10556.3.camel@cs180154> (raw)
In-Reply-To: <Pine.LNX.4.10.10207221352430.27914-100000@compaq.skyline.net>
On Mon, 2002-07-22 at 21:47, Hayden Myers wrote:
> Tcpdump output is where I'm seeing the difference in the clients receive
> window. Below is tcpdump from the server
>
> [root@install spinbox]# /usr/sbin/tcpdump src port 80
Your dump is showing only one direction of the connection. The receive
window visible in this dump is used for the reverse direction. Use
"tcpdump port 80" instead to get some useful output.
Linux 2.4 starts with a small receive window and rapidly increases it
when the data starts to flow. This is a type of receiver oriented
congestion control. You don't see the window increase here, because
there is very little data sent from client to server.
Also, next time try not to wrap the dump output. Beastly hard to make
sense of.
MikaL
next prev parent reply other threads:[~2002-07-22 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 23:30 2.2 to 2.4 migration Hayden Myers
2002-07-19 17:04 ` 2.2 to 2.4... serious TCP send slowdowns Hayden Myers
2002-07-20 20:53 ` Alan Cox
2002-07-22 18:47 ` Hayden Myers
2002-07-22 19:51 ` Mika Liljeberg [this message]
2002-07-23 7:24 ` Buddy Lumpkin
-- strict thread matches above, loose matches on Subject: below --
2002-07-19 20:09 Nivedita Singhvi
[not found] <Pine.LNX.4.10.10207221603340.4476-100000@compaq.skyline.net>
2002-07-22 20:32 ` Mika Liljeberg
[not found] <Pine.LNX.4.10.10207221646120.4476-100000@compaq.skyline.net>
2002-07-22 21:43 ` Mika Liljeberg
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=1027367487.10556.3.camel@cs180154 \
--to=mika.liljeberg@welho.com \
--cc=hayden@spinbox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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