Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!natinst.com!hrd769.brooks.af.mil!hrd769.brooks.af.mil!not-for-mail From: burgess@hrd769.brooks.af.mil (Dave Burgess) Newsgroups: comp.os.386bsd.bugs Subject: Re: ed0: warning - reciever ring buffer overflow Date: 20 Sep 1993 19:38:01 -0500 Organization: Armstrong Laboratory, Brooks AFB, TX Lines: 33 Message-ID: <27lidn$its@hrd769.brooks.af.mil> References: <CDoAxI.2y6@percy.rain.com> NNTP-Posting-Host: hrd769.brooks.af.mil In article <CDoAxI.2y6@percy.rain.com> davidg@percy.rain.com (David Greenman) writes: > It always surpises me that people don't just ask the original author >these questions. :-) Anyway, the reason these are happening is that the Just didn't occur to us I guess... >with full wire speeds...but the driver tries hard...so even though packets and does a commednable job, I might add. >get dropped, your performance only drops to about what the ethernet board >is capable of (should be in the 400-600k range with an 8bit card). NFS >is especially bad because the UDP window is quite large (40k last time I >looked), so the overflow condition can happen easily. I've explained this This ought to make our network engineers real happy, now they can blame software for their network problems again :-) >for the most part in the release notes for the driver, but these didn't >make it into either the FreeBSD or NetBSD releases (we couldn't find an >appropriate place to put them). The FAQ seems pretty appropriate to me. Check tomorrow and this whole section should be there -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX