From owner-freebsd-current@FreeBSD.ORG  Sat Aug 16 03:40:50 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D18D1106566B
	for <freebsd-current@freebsd.org>; Sat, 16 Aug 2008 03:40:50 +0000 (UTC)
	(envelope-from vehemens@verizon.net)
Received: from vms173001pub.verizon.net (vms173001pub.verizon.net
	[206.46.173.1]) by mx1.freebsd.org (Postfix) with ESMTP id C4DA08FC16
	for <freebsd-current@freebsd.org>; Sat, 16 Aug 2008 03:40:50 +0000 (UTC)
	(envelope-from vehemens@verizon.net)
Received: from sam ([71.107.11.239]) by vms173001.mailsrvcs.net
	(Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
	with ESMTPA id <0K5O00CWEA2U2TT7@vms173001.mailsrvcs.net> for
	freebsd-current@freebsd.org; Fri, 15 Aug 2008 21:40:07 -0500 (CDT)
Date: Fri, 15 Aug 2008 19:45:50 -0700
From: vehemens <vehemens@verizon.net>
To: freebsd-current@freebsd.org
Message-id: <200808151945.50696.vehemens@verizon.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
User-Agent: KMail/1.9.7
Subject: kernel memory
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Sat, 16 Aug 2008 03:40:50 -0000

I'm going to ask this question as I have not seen this rule written down 
anywhere.  So don't shoot me please :>

Do kernel memory memory routines such as malloc always return a region of 
memory that is locked to a physical page?