Date: Thu, 29 Apr 2010 17:18:38 -0500 From: "James R. Van Artsdalen" <james-freebsd-current@jrv.org> To: Scott Long <scottl@samsco.org> Cc: Tom Evans <tevans.uk@googlemail.com>, Ollivier Robert <roberto@keltia.freenix.fr>, freebsd-current@freebsd.org Subject: Re: kmem_map too small: 3832475648 total allocated Message-ID: <4BDA05BE.8090807@jrv.org> In-Reply-To: <E79134A9-2174-4905-85A6-ADAEC0EA7D66@samsco.org> References: <4BD8F7FA.2080103@jrv.org> <20100429145334.GB62822@roberto-al.eurocontrol.fr> <n2m2e027be01004290844k51dd6060q77375e894ff4efc4@mail.gmail.com> <E79134A9-2174-4905-85A6-ADAEC0EA7D66@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote: > > I'm sorry, but I find it absolutely absurd that any filesystem has to wire down 2GB of RAM, and that the solution to panics is buy more The only thing buying more RAM is likely to do is make the memory leak behind this harder to reproduce. Likewise increasing kernel tunables. It may only be a short-term leak, i.e. something that would be recovered normally. Does FreeBSD have a kernel debug facility for this? Is there a way to look at a kernel dump file and identify by caller who allocated space?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BDA05BE.8090807>