From owner-freebsd-current@FreeBSD.ORG Wed Jun 25 10:35:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 429F837B405 for ; Wed, 25 Jun 2003 10:35:43 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 70BC243FF7 for ; Wed, 25 Jun 2003 10:35:42 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 73291 invoked from network); 25 Jun 2003 17:35:41 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 25 Jun 2003 17:35:41 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 25 Jun 2003 12:35:17 -0500 (CDT) From: Mike Silbersack To: Terry Lambert In-Reply-To: <3EF95C9D.2CE63283@mindspring.com> Message-ID: <20030625123457.J7607@odysseus.silby.com> References: <20030625002841.X7607@odysseus.silby.com> <3EF95C9D.2CE63283@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Best way to get max KVA setting? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2003 17:35:43 -0000 On Wed, 25 Jun 2003, Terry Lambert wrote: > Mike Silbersack wrote: > > I could probably grep for this, but what's the best way to get a hold of > > the # of pages (or MB of ram) that max KVA is set to? I'm adding another > > autosize option, and I want to base it on min (KVA, ram) so that it > > doesn't balloon on boxes where ram >> KVA. > > I posted a patch about a month ago that did exactly this. > > It was for a guy who was was running with PAE enabled on an > 8G machine, and the autotuning was shooting him in the foot > when it tried to grab enough memory to create kmem_map entries > for the 8G of RAM in his 2G KVA space, and its head exploded. > > Let me know if you can't find it in the -current archives, and > I can dig it out for you, if you're willing to wait a day or > two. > > -- Terry I found the thread in question, but I didn't see a patch. Mike "Silby" Silbersack