From: Janne Pikkarainen <jaba@mikrobitti.fi>
To: walt <wa1ter@myrealbox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Via-Rhine ethernet driver problem?
Date: Mon, 29 Mar 2004 21:40:50 +0300 [thread overview]
Message-ID: <1080585650.1349.2.camel@cs95250.pp.htv.fi> (raw)
In-Reply-To: <40685BC9.1040902@myrealbox.com>
On Mon, 2004-03-29 at 20:24, walt wrote:
> Hi, Roger et al,
>
> ECS K7VTA3 motherboard with built-in ethernet chip:
>
> 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
> Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235
> Flags: bus master, medium devsel, latency 32, IRQ 11
> I/O ports at ec00 [size=256]
> Memory at e9041000 (32-bit, non-prefetchable) [size=256]
> Capabilities: [40] Power Management version 2
>
> The problem is terrible performance -- I noticed that NFS file transfers grind
> to a complete halt almost immediately on this machine.
>
> I also discovered by using 'scp' to copy files between machines that the bad
> performance is assymetrical: copying a file *to* this machine runs at about
> half-speed (5 MB/sec) whereas copying a file *from* this machine runs at
> 45 KiloB/sec, about one percent of expected.
>
> The reason I feel this is software and not hardware is that the same machine
> running any of the BSD's runs full-speed in both directions.
Hello,
I'm trying to take some load off from actual kernel developers and doing
just a small check: is your NIC in full duplex mode while in Linux?
Please check it with mii-tool or ethtool. This sounds like a half-duplex
problem for me...
Best Regards,
Janne Pikkarainen
next prev parent reply other threads:[~2004-03-29 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 17:24 walt
2004-03-29 18:36 ` Roger Luethi
2004-03-30 13:02 ` walt
2004-03-29 18:40 ` Janne Pikkarainen [this message]
2004-06-18 19:34 ` Bjoern Schmidt
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=1080585650.1349.2.camel@cs95250.pp.htv.fi \
--to=jaba@mikrobitti.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=wa1ter@myrealbox.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
all inboxes | Powered by JetHome®