Date: Thu, 26 Dec 1996 23:47:22 -0800 From: David Greenman <dg@root.com> To: Joe Greco <jgreco@solaria.sol.net> Cc: mango@staff.communique.net, questions@freefall.freebsd.org Subject: Re: Help 'no buffer available'!! Message-ID: <199612270747.XAA09693@root.com> In-Reply-To: Your message of "Thu, 26 Dec 1996 16:10:33 CST." <199612262210.QAA07831@solaria.sol.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>> >My kernel details"
>> >
>> >options "CHILD_MAX=512"
>> >options "OPEN_MAX=1024"
>> >options "MAXMEM=262144"
>> >options "NMBCLUSTERS=4096"
>> >options "EXTRAVNODES=30000" <----- this is not a real option on
>> >2.1.6
>> >options "NBUF=4096"
>>
>> I don't know off hand what is causing your problem, but you definately
>> don't want NBUF=4096. There is no reason for it and it will consume a
>> tremendous amount of virtual memory in 2.1.x.
>
>I have noticed I get the "No buffer space" under several conditions, most
>of which involve "stalls" of networking stuff.
>
>An enabled de interface with nothing connected will cause this.
>A sl interface that got flow controlled will often get wedged in this state.
ENOBUFS ("No buffer space available") can be returned for a lot of reasons.
One of them is when the interface output queue has reached the limit (usually
50 packets). If the interface output should get jammed for some reason such
as stuck flow control on a serial line, packets will back up in the queue
until the limit is reached and this error will be reported.
-DG
David Greenman
Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612270747.XAA09693>