From owner-freebsd-stable@FreeBSD.ORG Sun Mar 1 19:45:11 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A99D106566B for ; Sun, 1 Mar 2009 19:45:11 +0000 (UTC) (envelope-from alan.l.cox@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id F32DB8FC1E for ; Sun, 1 Mar 2009 19:45:10 +0000 (UTC) (envelope-from alan.l.cox@gmail.com) Received: by yw-out-2324.google.com with SMTP id 2so1157323ywt.13 for ; Sun, 01 Mar 2009 11:45:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=vu4Kv9tc4rJBa4A4yds2OypGImI0JVWJ7UVM06O0HSs=; b=RkwTsH3lHaHbo4ZZomhJmi5bQdXJQUzoUW8CpX3gWgFe6znIaaKVpOzvvDBTTg6ZxX He+Bd1ZEBa+4ysGxV1pCEPnzR7MG7J3XI/JNwBBpYe1EiIB8l1Twlm/DM7I/bMnZp3kd APxArV/ql7ghmndx4aYrtXANYf2hvYnWlKZRo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=bkrWdRIdrVPszaaLXz+eBk2k0whpVVW1p/pByMRzLOQtGVpq5EsIWzScGOnH98KN10 U48FEZZ6wcIZBvVlI4oeKNW4t3w4BEWFWmMwz4llg+rvW3BJ2UMzYtVdtMSpHGmXYjAh IBDO8XdJO1dNpjbrImyZI5yU+uZ35ur7NTToM= MIME-Version: 1.0 Received: by 10.150.150.19 with SMTP id x19mr464124ybd.229.1235936710306; Sun, 01 Mar 2009 11:45:10 -0800 (PST) In-Reply-To: References: <20090301031001.GB3465@dan.emsphone.com> Date: Sun, 1 Mar 2009 13:45:10 -0600 Message-ID: From: Alan Cox To: Pete French Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, dnelson@allantgroup.com Subject: Re: vm_thread_new: kstack allocation failed with vm.kmem_size="1536M" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: alc@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Mar 2009 19:45:11 -0000 On Sun, Mar 1, 2009 at 8:57 AM, Pete French wrote: > > I'm running 7-STABLE as of Feb 26 or so. Commit r187466 on Jan 20 bumped > up > > kmem_size_max on amd64 to 3.6GB: > > > > http://svn.freebsd.org/viewvc/base?view=revision&revision=187466 > > Mmmmm.... now I am wworried about upgrading to STABLE! ;) I can't > think of a reason why I am seeing what I am seeing - on 7.1-RELEASE > I am certainly icreasing the limits not decreasing them, yet I > am seeing it running out of memory on the larger limit. > > Note that these machines have no swap - but then since the system runs fine > on a 4gig machine with 4 gig of sap, I made the assumption that if > the machine was expanded to 8 gig of real memory it no longer needs the > swap, as it now has as much real RAM in it as real+swap was before. > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > When you adjust the kmem size, you are playing a zero-sum game. When you increase the kmem size, the additional space for the kernel's heap has to come from somewhere. One effect is that the available space for kernel thread stacks is reduced. If you're going to adjust kmem size, you should keep an eye on "sysctl vm.kvm_free". Regards, Alan