Date: Fri, 13 Jun 2003 14:46:09 -0400 (EDT) From: Jeff Roberson <jroberson@chesapeake.net> To: Terry Lambert <tlambert2@mindspring.com> Cc: current@freebsd.org Subject: Re: panic: kmem_map too small: the downside of FreeBSD 5 Message-ID: <20030613144256.D36168-100000@mail.chesapeake.net> In-Reply-To: <3EEA04BD.9E06ED0@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 13 Jun 2003, Terry Lambert wrote: > John Hay wrote: > > On a 5.1-RELEASE machine I have been able to cause a panic like this: > > panic: kmem_malloc(4096): kmem_map too small: 28610560 total allocated > > Manually tune your system. This panic results from the fact > that zone allocations with fixed limits don't really do the > right thing any more, now that it's possible to implement the > map entry allocations at interrupt. This is FUD. > the deprecation of the zalloci() interface that accompanied it, > an audit should have been done of the system to go through all > previous places zalloci() was used, and make them robust in case > of a NULL return value (allocation failure), since those places > were effectively promised by zalloci() that allocations would > never fail for this reason. > They would fail before. This is FUD. More FUD was deleted. 5.0 simply consumes more memory than 4.x. Unfortunately even with kernel memory taking up 1/3rd of your resources we are not able to satisfy all requests. Some tuning of various memory consumers would be required to get this back down. I think this is a worthwhile effort as we should be able to run on a 32mb system still. Please note that I'm about to get on a plane and I will probably not reply to this message. Thanks, Jeff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030613144256.D36168-100000>