From: Andreas Hartmann <andihartmann@freenet.de>
To: linux-kernel@vger.kernel.org
Subject: Re: TG3: very high CPU usage
Date: Mon, 19 Jan 2004 12:32:24 +0100 [thread overview]
Message-ID: <bugf88$932$1@A8bba.a.pppool.de> (raw)
In-Reply-To: <fa.eu7l1gd.ekqe1j@ifi.uio.no>
Mark Williams (MWP) wrote:
[...]
> However, when using Apache or any FTP client/daemon, the TG3 driver appears to be VERY slow maxing out CPU usage at 100% while only transfering at around 12MB/sec.
> This applies for both incoming or outgoing data.
[...]
> Ive tried other NICs, etc and confirmed that it is a problem with the TG3 driver.
I saw the same problem with the bcm-driver (Kernel 2.4.x) shipped with
SuSE 9 / SLES 8. Testcase was the initial mirror of a 10 GB partition on a
raid5 serveraid / XSeries 235 (2 way) to the same hardware on the remote
machine using both times the onboard NIC (Broadcom GBit Ethernet) via drbd:
100% CPU usage, 12 MB/s, machine is nearly death.
Regards,
Andreas Hartmann
next parent reply other threads:[~2004-01-19 11:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.eu7l1gd.ekqe1j@ifi.uio.no>
2004-01-19 11:32 ` Andreas Hartmann [this message]
2004-01-20 3:54 ` TG3: very high CPU usage 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
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
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
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='bugf88$932$1@A8bba.a.pppool.de' \
--to=andihartmann@freenet.de \
--cc=linux-kernel@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 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.