Date: Tue, 28 Sep 2010 16:39:05 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: stable@freebsd.org, Willem Jan Withagen <wjw@digiware.nl>, fs@freebsd.org Subject: Re: Still getting kmem exhausted panic Message-ID: <4CA1EFF9.1050802@icyb.net.ua> In-Reply-To: <20100928132355.GA63149@icarus.home.lan> References: <4CA1D06C.9050305@digiware.nl> <20100928115047.GA62142__15392.0458550148$1285675457$gmane$org@icarus.home.lan> <4CA1DDE9.8090107@icyb.net.ua> <20100928132355.GA63149@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
on 28/09/2010 16:23 Jeremy Chadwick said the following: > On Tue, Sep 28, 2010 at 03:22:01PM +0300, Andriy Gapon wrote: >> I believe that "the trick" is to set vm.kmem_size high enough, eitehr using this >> tunable or vm.kmem_size_scale. > > Thanks for the clarification. I just wish I knew how vm.kmem_size_scale > fit into the picture (meaning what it does, etc.). The sysctl > description isn't very helpful. Again, my lack of VM knowledge... > Roughly, vm.kmem_size would get set to <available memory> divided by vm.kmem_size_scale. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CA1EFF9.1050802>