From owner-freebsd-current@FreeBSD.ORG Wed Jun 25 01:27:27 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 4CB5037B401 for ; Wed, 25 Jun 2003 01:27:27 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2DA343F93 for ; Wed, 25 Jun 2003 01:27:26 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc0fm.dialup.mindspring.com ([209.86.1.246] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19V5ch-0003BA-00; Wed, 25 Jun 2003 01:27:24 -0700 Message-ID: <3EF95C9D.2CE63283@mindspring.com> Date: Wed, 25 Jun 2003 01:26:05 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Silbersack References: <20030625002841.X7607@odysseus.silby.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4a079f78e4f82e2a1ca453b415571b163666fa475841a1c7a350badd9bab72f9c350badd9bab72f9c 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 08:27:27 -0000 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