From owner-freebsd-stable@FreeBSD.ORG Thu May 10 15:52:36 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3B7A9106564A; Thu, 10 May 2012 15:52:36 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from ecbiz102.inmotionhosting.com (ecbiz102.inmotionhosting.com [70.39.235.94]) by mx1.freebsd.org (Postfix) with ESMTP id E6F378FC08; Thu, 10 May 2012 15:52:35 +0000 (UTC) Received: from 173-14-128-81-newengland.hfc.comcastbusiness.net ([173.14.128.81]:59327 helo=jack.bspruce.com) by ecbiz102.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1SSVfN-0001Z8-I1; Thu, 10 May 2012 11:52:33 -0400 Message-ID: <4FABE440.5000100@greatbaysoftware.com> Date: Thu, 10 May 2012 11:52:32 -0400 From: Charles Owens Organization: Great Bay Software User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: alc@freebsd.org References: <4FAAAF8E.40007@greatbaysoftware.com> In-Reply-To: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ecbiz102.inmotionhosting.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - greatbaysoftware.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Adam Vande More , Alan Cox , freebsd-stable@freebsd.org Subject: Re: superpages not solving "PV entries" limit warning X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2012 15:52:36 -0000 That's very helpful! I had read about that and wondered if it applied to i386. Should I have expected "superpages" to completely cure the condition... or does it just help? Should I now be looking at tuning the related pmap sysctls to give further relief? Thanks! Charles On 5/10/12 11:24 AM, Alan Cox wrote: > On Thu, May 10, 2012 at 2:32 AM, Adam Vande More > > wrote: > > On Wed, May 9, 2012 at 12:55 PM, Charles Owens > >wrote: > > > Hi fellow BSD-types, > > > > I have a buy system that forks lots of processes and I see > repeatedly the > > message: "Approaching the limit on PV entries, consider > increasing either > > the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable". > > > > System details: > > > > * 8.1-RELEASE-p2 i386 PAE kernel > > * 6 GB RAM > > > > The warning is not applicable any longer including your version as > well as > several previous ones. The warning has been removed from current > releases. > > > For amd64, yes, but not i386. It can't be removed from i386. > > Alan > > >