From: JG <jg@cms.ac>
To: linux-kernel@vger.kernel.org
Subject: Re: TG3: very high CPU usage
Date: Tue, 20 Jan 2004 13:33:58 +0100 [thread overview]
Message-ID: <20040120123406.6684B1A9932@23.cms.ac> (raw)
In-Reply-To: <20040119033527.GA11493@linux.comp>
[-- Attachment #1: Type: text/plain, Size: 2098 bytes --]
hi,
> iperf, between a 2.6.0 box and a WinXP box (both running Netgear GA302Ts with the AC9100), shows max throughput of 35MB/sec.
i have also two boxes (one with 2.6.0, the other one 2.6.1-mm2) equipped with netgear ga302t cards (x-over cable).
i don't see a very high cpu usage, but since upgrading to 2.6.x kernels i sometimes have really weird speed issues. i often only get transfer rates of about ~200-300 kilobytes/second...yes, and this over a gigabit interface, tested over ftp.
i'm also running a nfs server on the 2.6.1-mm2 box, the 2.6.0 pc is the client, but again, sometimes it's *very* slow. if i reboot my 2.6.1-mm2 box (the other one is a server which can't be rebooted) it seems to be fine for some time.
i didn't have such problems with 2.4.19 kernels on both pcs, there i got about 30-35MB/s over ftp without any problems, so i don't think it's hardware related.
lspci -v
2.6.1-mm2:
00:09.0 Ethernet controller: Altima (nee Broadcom) AC9100 Gigabit Ethernet (rev 15)
Subsystem: Netgear: Unknown device 302a
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 16
Memory at cffe0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] PCI-X non-bridge device.
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
2.6.0:
same as above, only other interrupt
this is also something i don't know how to debug, it is on the 2.6.0 box with an uptime of 7 days.
ifconfig:
eth1 Link encap:Ethernet HWaddr 00:09:5B:1F:1F:BC
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:217871027 errors:2769019 dropped:0 overruns:0 frame:2771160
TX packets:150029615 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2016894721 (1923.4 Mb) TX bytes:1073040436 (1023.3 Mb)
Interrupt:11
how can i find out where these errors come from?
thx,
JG
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-20 12:34 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 [this message]
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
[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=20040120123406.6684B1A9932@23.cms.ac \
--to=jg@cms.ac \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome