From owner-freebsd-current@FreeBSD.ORG  Tue Jun 24 11:19:37 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 1917D37B401
	for <freebsd-current@freebsd.org>;
	Tue, 24 Jun 2003 11:19:37 -0700 (PDT)
Received: from redux.oneway.com (redux.oneway.com [216.22.46.103])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5C92243F85
	for <freebsd-current@freebsd.org>;
	Tue, 24 Jun 2003 11:19:36 -0700 (PDT)	(envelope-from jay@oneway.com)
Received: from redux.oneway.com (localhost [127.0.0.1])
	by redux.oneway.com (8.12.5/8.12.5) with ESMTP id h5OIJA4m013655
	for <freebsd-current@freebsd.org>;
	Tue, 24 Jun 2003 14:19:10 -0400 (EDT)
Received: from localhost (jay@localhost)h5OIJ96B013652
	for <freebsd-current@freebsd.org>;
	Tue, 24 Jun 2003 14:19:10 -0400 (EDT)
X-Authentication-Warning: redux.oneway.com: jay owned process doing -bs
Date: Tue, 24 Jun 2003 14:19:09 -0400 (EDT)
From: Jay Kuri <jay@oneway.com>
To: freebsd-current@freebsd.org
Message-ID: <Pine.BSF.4.21.0306241406080.12240-100000@redux.oneway.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: questions about VM_KMEM_SIZE_SCALE
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2003 18:19:37 -0000


Hi there,

Can anyone shed some light on the implications of adjusting
VM_KMEM_SIZE_SCALE?  In particular I'm wondering if I increase this to,
say, 2, what happens?  I must admit I don't know how KVA is different from
KVM or total RAM... so the note in kern_malloc ("on an x86 with 256M KVA,
try to keep VM_KMEM_SIZE_MAX at 80M or below") doesn't shed enough light
on the matter.  What are the implications of VM_KMEM_SIZE getting large?

Does changing this affect memory available to user programs if it's unused
by the kernel?  

Thanks for any assistance,

Jay




- - - - - - - - - - - - - - - - - - - - - - - - - - - 
Nothing fails like success because you do not learn 
anything from it. The only thing we ever learn from 
is failure. Success only confirms our superstitions.

        Jay Kuri	 jay@oneway.com