From owner-freebsd-stable@FreeBSD.ORG Thu May 10 06:24:29 2012 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 CF514106566B for ; Thu, 10 May 2012 06:24:29 +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 8C2F78FC0C for ; Thu, 10 May 2012 06:24:29 +0000 (UTC) Received: from c-50-136-23-27.hsd1.nh.comcast.net ([50.136.23.27]:52070 helo=jack.bspruce.com) by ecbiz102.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1SSB6l-0006rq-T4 for freebsd-stable@freebsd.org; Wed, 09 May 2012 13:55:28 -0400 Message-ID: <4FAAAF8E.40007@greatbaysoftware.com> Date: Wed, 09 May 2012 13:55:26 -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: freebsd-stable@freebsd.org 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 Subject: 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 06:24:29 -0000 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". My research suggested that enabling the "superpages" feature via sysctl vm.pmap.pg_ps_enabled was the best action... that doing so would quite the warning and improve memory mapping efficiency. As far as I can tell, however, "superpages" haven't done this -- well, to be specific, I can say at least that they haven't quieted the warning. Since I'm still seeing the warning, do I need to tune something else? Other comments? System details: * 8.1-RELEASE-p2 i386 PAE kernel * 6 GB RAM Thanks very much! Charles -- Charles Owens Great Bay Software, Inc.