From: JG <jg@cms.ac>
To: Lincoln Dale <ltd@cisco.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: TG3: very high CPU usage
Date: Sun, 25 Jan 2004 13:31:46 +0100 [thread overview]
Message-ID: <20040125123154.A8CA4202CAA@23.cms.ac> (raw)
In-Reply-To: <5.1.0.14.2.20040125105347.02acce68@171.71.163.14>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
hi,
> urgh, those are terrible numbers!
yes ;)
> even an old Pentium3 @ 500MHz here is capable of pushing GbE wire-rate (i
> just tested this using a Tigon2).
my machines are athlon xp 1700+ and 2400+ so they should be fast enough...
> Fast Ethernet only uses 1 pair of wires each for Tx/Rx (4 wires), whereas
> copper GbE uses 2 pairs each for Tx/Rx (8 wires).
oh, yes, i didn't think of that (my bad...) because i thought "it worked with 2.4 kernels".
> if this is indeed simply an x-over cable, then i'd replace it and try again.
yes, they are located in different rooms and connected via an 20m x-over cable through the wall (easier than affording a gbit switch ;))
> Broadcom have a tool on their web site called "BACS" which [...] check the quality of the cable and report any
> problems it sees; it can run a signal/noise test on each pair.
thank you for the info! i searched their site, but i only found a reference to BACS on their faq page and that this software should be on their driver cdrom (well, it is not on my netgear cdrom).
but i'll test my cable with a fluke networks cable tester tomorrorw or on tuesday. i'll post the results if they are relevant.
i also tested with a knoppix cdrom on box2, which i can reboot, with 2.4.21 kernel and v1.5 tg3 driver, but the problem was also there so it really seems to be the cable...
thx,
JG
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-25 12:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 3:35 Mark Williams (MWP)
2004-01-20 12:33 ` JG
2004-01-20 23:13 ` Lincoln Dale
2004-01-21 3:19 ` Tom Sightler
2004-01-22 3:57 ` Lincoln Dale
2004-01-22 12:55 ` JG
2004-01-24 13:43 ` JG
2004-01-25 0:03 ` Lincoln Dale
2004-01-25 12:31 ` JG [this message]
2004-01-31 9:15 ` JG
2004-02-01 0:20 ` Lincoln Dale
2004-02-07 18:26 ` JG
2004-02-08 0:00 ` Lincoln Dale
2004-02-09 10:13 ` JG
2004-01-22 16:06 ` Tom Sightler
[not found] <fa.eu7l1gd.ekqe1j@ifi.uio.no>
2004-01-19 11:32 ` Andreas Hartmann
2004-01-20 3:54 ` Mark Williams (MWP)
[not found] <fa.g9joqss.1nneajs@ifi.uio.no>
[not found] ` <fa.e29fqcc.sick10@ifi.uio.no>
2004-01-20 9:17 ` Andreas Hartmann
2004-01-20 9:44 ` Lincoln Dale
2004-01-20 10:16 ` Mark Williams (MWP)
2004-01-20 12:09 ` Lincoln Dale
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=20040125123154.A8CA4202CAA@23.cms.ac \
--to=jg@cms.ac \
--cc=linux-kernel@vger.kernel.org \
--cc=ltd@cisco.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
Powered by JetHome