From owner-freebsd-current  Wed Jul  7 11:43:47 1999
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id DE6DD14D7D; Wed,  7 Jul 1999 11:43:44 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id LAA92954;
	Wed, 7 Jul 1999 11:43:44 -0700 (PDT)
	(envelope-from dillon)
Date: Wed, 7 Jul 1999 11:43:44 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199907071843.LAA92954@apollo.backplane.com>
To: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: Heh heh, humorous lockup
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

    Ok, but for a kernel hacker this *should* be funny.

    My system locked up because it had too much memory.  Specifically, there
    is a contrived limit to the size of the kernel malloc pool of 40MB,
    and 80MB for the entire pool based on VM_KMEM_SIZE_MAX.

    Unfortunately, if you have a lot of memory the vnode cache can actually
    wind up *using* 40MB, because the system isn't throwing away active 
    VM objects and so isn't throwing away vnodes.  

    Result: lockup.

    Since we have increased the hard page table allocation for the kernel to
    1G (?) we should be able to safely increase VM_KMEM_SIZE_MAX.  I was
    thinking of increasing it to 512MB.  This increase only effects 
    large-memory systems.  It keeps them from locking up :-)

    Anyone have any objections?

						-Matt



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message