From: Ken Brownfield <brownfld@irridia.com>
To: J Sloan <joe@tmsusa.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Recommendations about a 100/10 NIC
Date: Wed, 6 Mar 2002 11:15:02 -0600 [thread overview]
Message-ID: <20020306111502.D8107@asooo.flowerfire.com> (raw)
In-Reply-To: <3C82148E.E530824@wanadoo.es> <3C825A19.5070204@tmsusa.com>
In-Reply-To: <3C825A19.5070204@tmsusa.com>; from joe@tmsusa.com on Sun, Mar 03, 2002 at 09:15:05AM -0800
On Sun, Mar 03, 2002 at 09:15:05AM -0800, J Sloan wrote:
| In my humble experience with some hundreds
| of different Linux servers, the 3c905 seems the
| most trouble-free, and performs well.
Ah, I bet you didn't live through the truly atrocious 3Com drivers of
the past. ;) The new 3Com stuff seems passable for desktops, but having
been bitten dozens of times, I'm about 4^4^4^4 times shy.
| The Intel adapter has potential driver issues,
| although they seem to be getting resolved.
Haven't had any issues at all with eepro100 or e100 under production
load for years. Since Tulip went out of the mainstream (poor Digital)
the EtherExpress has been the most stable everywhere I've been. I've
written too many scripts for 3Com boxes that grep dmesg for "fatal"
errors and unload/reload the 3com module.
| The e100 driver has the disadvantage of being
| unable to work with the mii-tool commands,
Yes, and the fact that it "can't" be compiled-in.
| but seems to work well otherwise - as long as
| you don't mind trying to puzzle out whether
| the card is conected at 10 or 100, full or half.
That's all logged (dmesg, etc), if not distinctly queryable. Don't the
iANS tools allow this functionality, and more?
| The eepro100 driver works with mii-tool, but
| many have reported issues with the card dying
| under heavy use and needing to be reset. Many
| are using the eepro100 without problems - but
| the bottom line is that nobody is seeing these
| problems with the 3com cards.
Uhm, "nobody" is certainly not the proper word in this context. We've
pulled many 3Com cards because of issues, including ARP deafness,
overruns, hangs, etc. I have fully-saturated IDS systems running
eepro100 and e100 without issue, so heavy use may be necessary but is
not sufficient.
Oh, and six years of production on hundreds of EtherExpress NICs with
zero (0) issues. Obviously, not everyone sees every bug, but the
preponderance of evidence I've seen in production environments puts the
EE way ahead of 3Com. 3Com for Windows desktops works just fine.
I'd like to try existing Tulip hardware though for another option.
Though 8139too seems to work well.
--
Ken.
brownfld@irridia.com
|
| YMMV of course -
|
| Joe
|
|
| janvapan wrote:
|
| >What ethernet cards I should use for Linux 2.4?.
| >I am looking for a NIC based on stability and performance.
| >In short, Intel PRO/100 S Desktop Adapter(e100 driver) or
| >3Com 10/100 3C905C-TX-M(3c59x driver) ?
| >
|
|
| -
| To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-03-06 17:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-03 12:18 Recommendations about a 100/10 NIC janvapan
2002-03-03 14:22 ` Justin Piszcz
2002-03-03 20:29 ` Bernd Eckenfels
2002-03-03 21:04 ` Hans-Christian Armingeon
2002-03-04 3:05 ` rddunlap
2002-03-03 21:37 ` Hans-Christian Armingeon
2002-03-03 17:15 ` J Sloan
2002-03-03 20:39 ` LA Walsh @ tlinx.org
2002-03-04 1:04 ` J Sloan
2002-03-07 8:21 ` Kelsey Hudson
2002-03-06 17:15 ` Ken Brownfield [this message]
2002-03-06 17:36 ` John Jasen
2002-03-06 17:28 ` Tim Hockin
2002-03-06 18:30 ` Michael Sterrett -Mr. Bones.-
2002-03-06 18:33 ` John Jasen
2002-03-06 21:42 ` Francois Romieu
2002-03-08 1:47 ` Ken Brownfield
2002-03-07 5:06 ` J Sloan
2002-03-07 8:16 ` Kelsey Hudson
[not found] <Pine.LNX.4.10.10203031559090.801-100000@oakley.chf>
2002-03-03 16:25 ` Justin Piszcz
2002-03-04 5:15 ` Mike Fedyk
2002-03-04 9:54 ` Vojtech Pavlik
[not found] <fa.fifmv4v.ogc1qa@ifi.uio.no>
[not found] ` <fa.jgnh1iv.1ek48ih@ifi.uio.no>
2002-03-04 6:49 ` Dan Maas
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=20020306111502.D8107@asooo.flowerfire.com \
--to=brownfld@irridia.com \
--cc=joe@tmsusa.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