From: Baruch Even <baruch@ev-en.org>
To: netdev@oss.sgi.com
Cc: "David S. Miller" <davem@davemloft.net>,
Stephen Hemminger <shemminger@osdl.org>
Subject: TCP performance drop 2.6.6->2.6.7
Date: Tue, 12 Apr 2005 23:18:35 +0100 [thread overview]
Message-ID: <425C493B.5040206@ev-en.org> (raw)
Hello,
I'm trying to port my H-TCP and SACK improvements to 2.6.11, but I seem
to hit performance problems that are unrelated to what I worked on so far.
My tests show that between 2.6.6 and 2.6.7 the TCP performance dropped
considerably.
The setup for the tests, vanilla kernels, dummynet with 100 Mbit/s and
40ms rtt using the BIC protocol. No patches applied whatsoever.
iperf tests for 2.6.6 get about 90Mbit/s while 2.6.7 gets 30Mbit/s.
I was wondering if someone can think of a reason why this happens?
Is there a way to get the different network related patches between
these two versions? I don't have access to bk to get it myself.
Baruch
next reply other threads:[~2005-04-12 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 22:18 Baruch Even [this message]
2005-04-12 22:47 ` TCP performance drop 2.6.6->2.6.7 David S. Miller
2005-04-12 23:07 ` Stephen Hemminger
2005-04-12 23:59 ` Baruch Even
2005-04-13 18:20 ` Stephen Hemminger
2005-04-15 14:37 ` Baruch Even
2005-04-15 15:30 ` Nivedita Singhvi
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=425C493B.5040206@ev-en.org \
--to=baruch@ev-en.org \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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.