From owner-cvs-all@FreeBSD.ORG Tue Aug 3 03:23:11 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47B9416A4CF; Tue, 3 Aug 2004 03:23:11 +0000 (GMT) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2278F43D2F; Tue, 3 Aug 2004 03:23:11 +0000 (GMT) (envelope-from alc@cs.rice.edu) Received: from localhost (calypso.cs.rice.edu [128.42.1.127]) by cs.rice.edu (Postfix) with ESMTP id 6C9634B08A; Mon, 2 Aug 2004 22:23:10 -0500 (CDT) Received: from cs.rice.edu ([128.42.1.30]) by localhost (calypso.cs.rice.edu [128.42.1.127]) (amavisd-new, port 10024) with LMTP id 00384-01-52; Mon, 2 Aug 2004 22:23:10 -0500 (CDT) Received: by cs.rice.edu (Postfix, from userid 19572) id 0F5114B077; Mon, 2 Aug 2004 22:23:10 -0500 (CDT) Date: Mon, 2 Aug 2004 22:23:09 -0500 From: Alan Cox To: David O'Brien Message-ID: <20040803032309.GV18577@cs.rice.edu> References: <200408022152.i72Lqhig042925@repoman.freebsd.org> <410EE627.8090105@freebsd.org> <20040803013628.GU18577@cs.rice.edu> <20040803022413.GA17554@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040803022413.GA17554@dragon.nuxi.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: by amavis-20030616-p7 at cs.rice.edu cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: Scott Long cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Aug 2004 03:23:11 -0000 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