From owner-freebsd-bugs@FreeBSD.ORG Sun Jun 15 10:40:13 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04F8137B401 for ; Sun, 15 Jun 2003 10:40:13 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C2A443F93 for ; Sun, 15 Jun 2003 10:40:12 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h5FHeCUp091055 for ; Sun, 15 Jun 2003 10:40:12 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h5FHeCsO091054; Sun, 15 Jun 2003 10:40:12 -0700 (PDT) Date: Sun, 15 Jun 2003 10:40:12 -0700 (PDT) Message-Id: <200306151740.h5FHeCsO091054@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Jason Kuri Subject: Re: kern/53350: fill up a malloc md-disk on 5.1-R causes panic X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jason Kuri List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jun 2003 17:40:13 -0000 The following reply was made to PR kern/53350; it has been noted by GNATS. From: Jason Kuri To: "Poul-Henning Kamp" Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/53350: fill up a malloc md-disk on 5.1-R causes panic Date: Sun, 15 Jun 2003 12:35:02 -0500 Adding ram is not an option, as we need to be able to run this on different machines with different configs. Is there a way to determine at run-time how much kernel mapped memory is available for use? I have determined that adding -o reserve will cause the initial mdconfig to fail if the space is not available... Is there any documentation anywhere on the issues related to kernel mapped memory and allocation? Is this tunable at run time, and if not, can you point me to some information on how to properly use VM_KMEM_SIZE_SCALE (which I'm assuming is the right option) ? And one final question, am I right in thinking that increasing this will make less memory available for user processes even if the space is unused by the kernel? Thanks, Jay On Sunday, June 15, 2003, at 11:56 AM, Poul-Henning Kamp wrote: > In message , Jason > Kuri writes > : >> Ok, so speaking practically, how do I deal with this issue? I have a >> script that needs to be able to cache directories in ram... > > You add more RAM or change the fraction of RAM assigned to KVM. > I can't remember if this is documented somewhere. > > mdconfig(8) would have a hard time being able to tell when to reject > a request, and for testing purposes, it is a very convenient thing > to be able to create 1TB devices (and this works, as long as you > don't fill it with more data than you have KVM to). > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by > incompetence. >