Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!nntp-server.caltech.edu!glt
From: glt@cco.caltech.edu (Greg Tanaka)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: nfsd-udp very cpu hungry...
Date: 9 Jul 1993 06:31:11 GMT
Organization: California Institute of Technology, Pasadena
Lines: 26
Message-ID: <21j3bfINNeaf@gap.caltech.edu>
References: <21gnsn$26s@sun.rhbnc.ac.uk> <1993Jul8.104735.16179@cnplss5.cnps.philips.nl>
NNTP-Posting-Host: punisher.caltech.edu
y
ep the problem is definitely the ne2000 driver. I also have a 486/66 c
ompute\
r, and when it was using the ne2000 driver, it would come to a virtual stand s\
till...during NFS services. You could barely telnet in.... Not
only did itgobable
Auto-s up cpu time, it also transfers ed file
s at a max 75k (according to my stopwatch..). However, when I switch to a wd
8013 card, I got up to 6 timesthe rates and absolutely no visible slow
down in the computer. Oh yeah, this
was also after I upgrad
Auto-saving...done ed to the NetBSD-curre
nt sources with the new ed drive
r\
... Not only does the ne2000 driver have problems with performance, it also
has problems with theo's ifconfig -a... somehow it only manages to spit out
the parameters for the ne0, and give four inappropriate i
Auto-saving...done otc ctls.. very
depressing. I don't think the problem is with the ne2000 card. With commerci
\
al software like FTP's, my ne2000 actually transfers faster than my w
d8013!!
-Greg Tanaka
p.s. I hope it is just my screen that got messed up and not the message..