From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, dax@gurulabs.com (Dax Kelson)
Subject: Re: Xircom RealPort versus 3COM 3C3FEM656C
Date: Tue, 22 May 2001 14:18:28 -0700 [thread overview]
Message-ID: <200105222118.f4MLISL01588@moisil.badula.org> (raw)
In-Reply-To: <E152HYH-0002LB-00@the-village.bc.nu>
On Tue, 22 May 2001 20:10:41 +0100 (BST), Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Before you give up on the xircom thing, try the -ac kernel and set the box
> up to use xircom_cb not xircom_tulip_cb
>
> That might help a lot
It doesn't, it still performs poorly with any of the three available
drivers -- xircom_cb, xircom_tulip_cb, and tulip_cb (from the pcmcia package):
* Rx gets only about 1.8Mbit/s on a 100Base-TX network with any of the three
* Tx gets 80+Mb/s with xircom_tulip_cb and tulip_cb, and less than 30Mb/s
with xircom_cb.
And no, promisc mode played no role in this experiment, because my test
network is switched and otherwise very quiet.
Windows drivers handle both Rx and Tx at full speed.
I have this feeling that we're handling the card in some (tulip) compat
mode, which severely cripples performance. It's hard to tell, without
docs...
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
next prev parent reply other threads:[~2001-05-22 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 18:33 Changes in Kernel Prasad
2001-05-22 18:20 ` Alan Cox
2001-05-22 18:28 ` H. Peter Anvin
2001-05-22 18:47 ` Vivek Dasmohapatra
2001-05-22 19:07 ` Xircom RealPort versus 3COM 3C3FEM656C Dax Kelson
2001-05-22 19:10 ` Alan Cox
2001-05-22 19:35 ` Jeff Garzik
2001-05-22 21:18 ` Ion Badulescu [this message]
2001-05-22 21:34 ` arjan
2001-05-22 22:13 ` Ion Badulescu
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=200105222118.f4MLISL01588@moisil.badula.org \
--to=ionut@moisil.cs.columbia.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dax@gurulabs.com \
--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
all inboxes | Powered by JetHome®