From: Stephen Hemminger <shemminger@osdl.org>
To: "Eshwar" <eshwar@moschip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: TCP Network performance degade from 2.4.18 to 2.6.10
Date: Wed, 28 Sep 2005 09:35:54 -0700 [thread overview]
Message-ID: <20050928093554.418b79a2@localhost.localdomain> (raw)
In-Reply-To: <LEXUSAX3cf3ednHM3SO00000be8@lexus.moschip.com>
On Wed, 28 Sep 2005 10:42:22 +0530
"Eshwar" <eshwar@moschip.com> wrote:
> HI all,
>
> I observed there is huge network performance drop from linux 2.4 to 2.6 with
> the same setup (No hardware changes..). The results are taken in PIV
> processor with D-Link network card... with iperf ... Can some body help me
> why such a huge difference... in TCP stream...
>
> In linux 2.4 (Redhat 9)
>
> DLink
> TCP UDP
> Tx 94.3Mbps Tx 95 Mbps
> Rx 94.2 Mbps Rx 95 Mbps
>
> In linux 2.6.10 (Fedora Core 4)
> DLink
> TCP UDP
> Tx 64.3 Mbps Tx 87 Mbps
> Rx 88.1 Mbps Rx 95 Mbps
>
>
> Thanks & Regards
> Eshwar
Please send network performance discussion to netdev@vger.kernel.org
A lot more information is needed, like:
* which hardware is on both ends of the test (lscpci)
* any TCP configuration issues
* any errors reported.
* netfilter and firewalling.
parent reply other threads:[~2005-09-28 16:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <LEXUSAX3cf3ednHM3SO00000be8@lexus.moschip.com>]
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=20050928093554.418b79a2@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=eshwar@moschip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).