From owner-freebsd-questions@FreeBSD.ORG  Tue May  6 15:03:36 2008
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 13E271065676
	for <freebsd-questions@freebsd.org>;
	Tue,  6 May 2008 15:03:36 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from parsely.rain.com (parsely.rain.com [199.26.172.196])
	by mx1.freebsd.org (Postfix) with ESMTP id 8AB068FC1E
	for <freebsd-questions@freebsd.org>;
	Tue,  6 May 2008 15:03:35 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from sopwith.solgatos.com (uucp@localhost)
	by parsely.rain.com (8.11.4/8.11.4) with UUCP id m46F3FP79538;
	Tue, 6 May 2008 08:03:15 -0700 (PDT)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from localhost by sopwith.solgatos.com (8.8.8/6.24)
	id PAA11211; Tue, 6 May 2008 15:01:39 GMT
Message-Id: <200805061501.PAA11211@sopwith.solgatos.com>
To: Giorgos Keramidas <keramida@ceid.upatras.gr>,
	Mel <fbsd.questions@rachie.is-a-geek.net>, freebsd-questions@freebsd.org
In-reply-to: Your message of "Sun, 13 Apr 2008 01:00:41 +0300."
	<87ve2m7mye.fsf@kobe.laptop> 
Date: Tue, 06 May 2008 08:01:39 +0100
From: Dieter <freebsd@sopwith.solgatos.com>
Cc: 
Subject: Re: 6.2 -> 7.0 now mlock(2) fails 
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2008 15:03:36 -0000

> It is.  The pageout daemon initializes max_wired with:
> 
>         /* XXX does not really belong here */
>         if (vm_page_max_wired == 0)
>                 vm_page_max_wired = cnt.v_free_count / 3;
> 

I installed the following:

diff -r1.1 vm_pageout.c
1421c1421,1425
<               vm_page_max_wired = cnt.v_free_count / 3;
---
>         {
>           printf("vm_page_max_wired was 0.  cnt.v_free_count / 3 = %d\n", cnt.v_free_count / 3);
>           printf("setting vm_page_max_wired to cnt.v_free_count / 2 = %d\n", cnt.v_free_count / 2);
>           vm_page_max_wired = cnt.v_free_count / 2;
>         }

Which gives:

vm_page_max_wired was 0.  cnt.v_free_count / 3 = 165410
setting vm_page_max_wired to cnt.v_free_count / 2 = 248115

No mlock failures in ~2.5 weeks.
The largest value logged for vm.stats.vm.v_wire_count is 188614.

Thanks!