From owner-freebsd-current@FreeBSD.ORG  Thu Apr 29 00:48:48 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id C20EB16A4CE; Thu, 29 Apr 2004 00:48:48 -0700 (PDT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 756EF43D4C; Thu, 29 Apr 2004 00:48:45 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i3T7ma7E066473;
	Thu, 29 Apr 2004 00:48:39 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200404290748.i3T7ma7E066473@gw.catspoiler.org>
Date: Thu, 29 Apr 2004 00:48:36 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: green@FreeBSD.org
In-Reply-To: <200404290008.i3T08HaS004242@green.homeunix.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: alc@FreeBSD.org
cc: bms@FreeBSD.org
cc: current@FreeBSD.org
Subject: Re: VM wiring fixed
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Apr 2004 07:48:48 -0000

On 28 Apr, Brian Fundakowski Feldman wrote:

> * vm_map_{un,}wire() did not keep track of wirings as they should.  User
>   wirings are separate from system wirings, and there can be exactly one.
>   There can be unlimited system wirings, but wired_count will remain at
>   zero for map entries that are allocated as MAP_ENTRY_NOFAULT.

This is something that I started to worry about when I was making my
mlock()/vslock() changes a while back.  I was hoping to find time to
mention my concerns, but I never accumulated enough round tuits.  I'm
really glad to see attention paid to this issue.