From: Paul Dickson <dickson@permanentmail.com>
To: linux-os@analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Network speed Linux-2.6.10
Date: Tue, 1 Mar 2005 17:51:43 -0700 [thread overview]
Message-ID: <20050301175143.04cbbe64.dickson@permanentmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503011426180.578@chaos.analogic.com>
On Tue, 1 Mar 2005 14:29:24 -0500 (EST), linux-os wrote:
> Intel NIC e100 device driver. Two identical machines.
> Private network, no other devices. Connected using a Netgear switch.
> Test data is the same thing sent from memory on one machine
> to a discard server on another, using TCP/IP SOCK_STREAM.
>
> If I set both machines to auto-negotiation OFF and half duplex,
> I get about 9 to 9.5 megabytes/second across the private wire
> network.
>
> If I set one machine to full duplex and the other to half-duplex
> I get 10 to 11 megabytes/second transfer across the network,
> regardless of direction.
>
> If I set both machines to auto-negotiation OFF and full duplex,
> I get 300 to 400 kilobytes/second regardless of the direction.
Might this be related to the broken BicTCP implementations in the 2.6.6+
kernels? A fix was added around 2.6.11-rc3 or 4.
-Paul
next prev parent reply other threads:[~2005-03-02 0:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 19:29 Network speed Linux-2.6.10 linux-os
2005-03-01 20:20 ` Ben Greear
2005-03-01 20:24 ` Lee Revell
2005-03-01 20:27 ` linux-os
2005-03-01 20:30 ` Miquel van Smoorenburg
2005-03-01 20:36 ` Lee Revell
2005-03-01 20:30 ` Ben Greear
2005-03-01 20:35 ` Lee Revell
2005-03-02 16:16 ` venom
2005-03-02 16:14 ` venom
2005-03-02 17:40 ` Horst von Brand
2005-03-02 17:48 ` linux-os
2005-03-01 20:26 ` linux-os
2005-03-01 20:34 ` Ben Greear
2005-03-02 0:51 ` Paul Dickson [this message]
2005-03-02 1:02 ` Baruch Even
2005-03-02 3:24 ` Paul Dickson
2005-03-02 9:37 ` Baruch Even
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=20050301175143.04cbbe64.dickson@permanentmail.com \
--to=dickson@permanentmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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