Date: Mon, 2 Aug 2004 22:23:09 -0500 From: Alan Cox <alc@cs.rice.edu> To: David O'Brien <obrien@freebsd.org> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c Message-ID: <20040803032309.GV18577@cs.rice.edu> In-Reply-To: <20040803022413.GA17554@dragon.nuxi.com> References: <200408022152.i72Lqhig042925@repoman.freebsd.org> <410EE627.8090105@freebsd.org> <20040803013628.GU18577@cs.rice.edu> <20040803022413.GA17554@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 02, 2004 at 07:24:13PM -0700, David O'Brien wrote: > > ... > > In short, VM_KMEM_SIZE_MAX needs to increase on i386. I just don't > > know how large of an increase is safe. Do you have access to an i386 > > with 4+ GB of RAM? > > I do -- and it is the machine that was panicing with: > > panic: kmem_malloc(4096): kmap_map too small: 209715200 total allocated > > Scottl told me the root cause was probably too high a kern.maxvnodes > value and that he's been telling many people to limit kern.maxvnodes to > 100000 (but I see he now likes a larger number...). > > vm.kmem_size: 209715200 > hw.physmem: 3883290624 > hw.usermem: 3751428096 > > are my current values. What can I do to help choose a better > VM_KMEM_SIZE_MAX capping? > For starters, please send me the results of "sysctl kern vm" off list. Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040803032309.GV18577>