From owner-freebsd-current Thu Jan 21 14:24:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06166 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:24:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06152 for ; Thu, 21 Jan 1999 14:23:57 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id OAA19995; Thu, 21 Jan 1999 14:19:26 -0800 (PST) Message-Id: <199901212219.OAA19995@implode.root.com> To: Mike Smith cc: Geoff Buckingham , freebsd-current@FreeBSD.ORG Subject: Re: KVA/KVM shortages In-reply-to: Your message of "Thu, 21 Jan 1999 13:53:44 PST." <199901212153.NAA11404@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 21 Jan 1999 14:19:26 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with >> 768MB RAM) poking about in the code adding: >> >> options "VM_KMEM_SIZE=(24*1024*1024)" >> options "VM_KMEM_SIZE_MAX=(128*1024*1024)" >> >> seems like a good way foward. Is it? > >>From what I can see, you shouldn't need to set VM_KMEM_SIZE_MAX unless >you're also setting VM_KMEM_SIZE_SCALE. > >I just committed a tweak that allows you to say: > > set kern.vm.kmem.size= > >at the loader prompt or in /boot/loader.rc to override the default >VM_KMEM_SIZE value. > >If anyone has any more of these tunables that can easily be enhanced >like this, please let me know. Is there a way from the boot loader that one can find out what options are available to be tuned? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message