From owner-cvs-src@FreeBSD.ORG Tue Aug 3 02:24:17 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D51A16A4CE; Tue, 3 Aug 2004 02:24:17 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88CBC43D60; Tue, 3 Aug 2004 02:24:16 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.13.1/8.12.11) with ESMTP id i732OErf017746; Mon, 2 Aug 2004 19:24:14 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i732OD1B017745; Mon, 2 Aug 2004 19:24:13 -0700 (PDT) (envelope-from obrien) Date: Mon, 2 Aug 2004 19:24:13 -0700 From: "David O'Brien" To: Alan Cox Message-ID: <20040803022413.GA17554@dragon.nuxi.com> References: <200408022152.i72Lqhig042925@repoman.freebsd.org> <410EE627.8090105@freebsd.org> <20040803013628.GU18577@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040803013628.GU18577@cs.rice.edu> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 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-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Aug 2004 02:24:17 -0000 On Mon, Aug 02, 2004 at 08:36:28PM -0500, Alan Cox wrote: > On Mon, Aug 02, 2004 at 07:11:03PM -0600, Scott Long wrote: > > David E. O'Brien wrote: > > > > >obrien 2004-08-02 21:52:43 UTC > > > > > > FreeBSD src repository > > > > > > Modified files: > > > sys/kern vfs_subr.c > > > Log: > > > Put a cap on the auto-tuning of kern.maxvnodes. > > > > > > Cap value chosen by: scottl > > > > > > Revision Changes Path > > > 1.518 +8 -0 src/sys/kern/vfs_subr.c > > > > Well, the number that I gave was really only a suggestion and is > > far too low to be useful on in a production environment like > > squid or a mail/imap server. What we should really be doing is > > scaling based on the size of the kmem_map. We should also be > > scaling kmem_map based on the size of physical RAM and not capping > > it to such relatively low values like we do right now. I'm also > > quite afraid of what might happen to something like squid that > > will be exerting both vnode and mbug pressure at the same time. > > It does scale with the amount of physical memory. There is, however, > an architecture-specific cap to account for the KVA size. This cap > is now too low, particularly, on i386. > > 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? -- -- David (obrien@FreeBSD.org)