Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!netnews.com!netaxs.com!grr From: grr@shandakor.tharsis.com (George Robbins) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: ETHER_MAX_LEN Date: 17 Apr 1997 06:39:50 GMT Organization: George's Pet Unix System Lines: 23 Message-ID: <slrn5lbhcg.2dc.grr@shandakor.tharsis.com> References: <Pine.OSF.3.95q.970416200912.26415A-100000@stat.WPI.EDU> NNTP-Posting-Host: robbins.jvnc.net X-Newsreader: slrn (0.9.1.1 BETA UNIX) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.netbsd.misc:5828 In article <Pine.OSF.3.95q.970416200912.26415A-100000@stat.WPI.EDU>, robert mcdonald wrote: >I complained about repeated "Receiver ring buffer overrun" messages... >and someone suggested I comment out the line that logs the error in the >kernel source file if_ed.c >looking through this source, I see ETHER_MAX_LEN defined as 1518. >Does this macro define the maximum size of an ethernet packet? >(I want to increase it to avoid the errors if possible...) That won't do it. The problem you're seeing is simply that ethernet traffic is coming in quicker than your machine can process it. The ethernet hardware take care of the overhead of reciving the data, but has a limited number of buffers to queue incoming data packets. Depending on the implementation, the amount of buffering is determined by the size of the local/dual-ported memory attached to the ethernet chip and not really easy to change. Your alternatives are, loosely speaking, get a more powerful machine that can keep up with the flow, get a quieter ethernet (like behind a router) or comment out the messages, since it is basically advisory and not an indication of an un-recoverable error. -- George Robbins - not working for, work: to be avoided at all costs... but still emotionally attached to: web: http://www.netaxs.com/people/grr Commodore, Engineering Department domain: grr@tharsis.com