From owner-freebsd-hackers Thu Jul 9 09:39:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08819 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 09:39:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08808 for ; Thu, 9 Jul 1998 09:38:58 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA05779; Thu, 9 Jul 1998 09:41:02 -0700 (PDT) Date: Thu, 9 Jul 1998 09:41:02 -0700 (PDT) From: Jim Shankland Message-Id: <199807091641.JAA05779@biggusdiskus.flyingfox.com> To: sbabkin@dcn.att.com, smoergrd@oslo.geco-prakla.slb.com Subject: Re: NIC drivers Cc: hackers@FreeBSD.ORG, mike@smith.net.au Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) writes: > Believe me, [the ep driver] still sucks. Search the archives (both the > mailing list archives and the PR database) for "no buffer space", > and/or "ep0". Basically, the driver is fine for telnet and mail, but > wedges under sustained load. I can get it to hang without ever going > above 20 kBps (160 kbps). Gimme an Intel EtherExpress. That was not my experience. We ran 4 3C509's in 1 box a few years ago (FreeBSD 2.1.?), and hammered them pretty hard, and it all just worked. Granted, we did retire the cards, and the 486 box they were in, some time ago. The Intel cards and the fxp driver are great. Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message