From: Ben Greear <greearb@candelatech.com>
To: linux-os@analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Network speed Linux-2.6.10
Date: Tue, 01 Mar 2005 12:34:39 -0800 [thread overview]
Message-ID: <4224D1DF.30909@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503011523330.706@chaos.analogic.com>
linux-os wrote:
> On Tue, 1 Mar 2005, Ben Greear wrote:
> I supplied the actual settings.
>
>> What happens if you just don't muck with the NIC and let it
>> auto-negotiate
>> on it's own?
>>
>
> It goes to half-duplex and runs 9 to 9.5 megabytes/second as stated
> above.
>
> That's why I think 1/2 duplex is __really__ full-duplex.
half-duplex will run near line speed in one direction. Try sending in
both directions at the same time and you'll get closer to 40% of the
link utilization... Also, if you see any collisions you are in half-duplex
mode.
You could try connecting the NICs back-to-back with a cross-over
cable to take your switch out of the loop?
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-03-01 20:35 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 [this message]
2005-03-02 0:51 ` Paul Dickson
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=4224D1DF.30909@candelatech.com \
--to=greearb@candelatech.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