From owner-cvs-src@FreeBSD.ORG Sat Mar 29 23:34:50 2003 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07D1237B405 for ; Sat, 29 Mar 2003 23:34:50 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 5C00B43FCB for ; Sat, 29 Mar 2003 23:34:48 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 71706 invoked from network); 30 Mar 2003 07:34:46 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 30 Mar 2003 07:34:46 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sun, 30 Mar 2003 01:31:18 -0600 (CST) From: Mike Silbersack To: Jake Burkholder In-Reply-To: <20030330070723.GE21973@locore.ca> Message-ID: <20030330012410.I3292@odysseus.silby.com> References: <200303300524.h2U5Ora7061852@repoman.freebsd.org> <20030330061301.GC21973@locore.ca> <20030330070723.GE21973@locore.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: HEADS UP Re: cvs commit: src/sys/conf options.i386 src/sys/i386/i386 bios.c locore.s machdep.c mpboot.s pmap.c vm86bios.s vm_machdep.c src/sys/i386/include _types.h bus_at386.h param.h pmap. X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 07:34:52 -0000 On Sun, 30 Mar 2003, Jake Burkholder wrote: > To clarify that the ram above 4G is used for, it just goes into the general > page pool. I don't intend to implement a means for user process's to access > more then their ~2.5G address space through a sliding window as has been done > on other systems, but this should be quite easy to do should someone be so > inclined. To give an example, on a 6G system you see things like this: Cool, that's much better than the situation was for large ram machines before. :) Do these changes allow something like a 3G KVA space without shrinking processes address spaces? Also, I'm assuming that PAE can boot on machines with < 4 Gig of ram; can it also be coaxed into acting in such a manner than busdma is _required_, so that a 256MB i386 box can be used to see if a driver is busdma compliant? In any case, very cool. Mike "Silby" Silbersack