From owner-freebsd-amd64@FreeBSD.ORG  Thu Jul 21 18:58:17 2005
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
X-Original-To: freebsd-amd64@freebsd.org
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D136916A427
	for <freebsd-amd64@freebsd.org>; Thu, 21 Jul 2005 18:58:17 +0000 (GMT)
	(envelope-from pete@he.iki.fi)
Received: from rms06.rommon.net (rms06.rommon.net [212.54.5.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 93BAD43D55
	for <freebsd-amd64@freebsd.org>; Thu, 21 Jul 2005 18:58:14 +0000 (GMT)
	(envelope-from pete@he.iki.fi)
Received: from [193.64.42.239] (dyn239.helenius.fi [193.64.42.239])
	by rms06.rommon.net (Postfix) with ESMTP id 6AEFB33C65;
	Thu, 21 Jul 2005 21:58:11 +0300 (EEST)
Message-ID: <42DFF043.3090203@he.iki.fi>
Date: Thu, 21 Jul 2005 21:58:11 +0300
From: Petri Helenius <pete@he.iki.fi>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Peter Wemm <peter@wemm.org>
References: <42DFDCCA.8050207@he.iki.fi> <200507210137.29816.peter@wemm.org>
In-Reply-To: <200507210137.29816.peter@wemm.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-amd64@freebsd.org
Subject: Re: kernel memory
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2005 18:58:18 -0000

Peter Wemm wrote:

>
>2GB for paged kernel memory.  But in addition we access memory via the 
>direct map area to avoid the need for temporary mappings in many cases.  
>uma (malloc, mbufs) etc use this, as does the sfbuf temporary mapping 
>system.
>
>  
>
So there is no limitation for malloced memory? Say if my driver would 
like to have 4 or 8 gig lookup cache that would work?

Pete