From owner-freebsd-chat@FreeBSD.ORG Fri Apr 28 12:07:01 2006 Return-Path: X-Original-To: freebsd-chat@freebsd.org Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B563116A402 for ; Fri, 28 Apr 2006 12:07:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3421743D46 for ; Fri, 28 Apr 2006 12:07:01 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3SC6wDr090609; Fri, 28 Apr 2006 08:06:58 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-chat@freebsd.org Date: Fri, 28 Apr 2006 07:40:06 -0400 User-Agent: KMail/1.8.3 References: <200604211034.k3LAY0TP096656@lurza.secnetix.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604280740.06963.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1428/Thu Apr 27 14:39:31 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Francisco Reyes Subject: Re: What ever happened to Terasolutions? X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2006 12:07:01 -0000 On Thursday 27 April 2006 07:03 pm, Francisco Reyes wrote: > Oliver Fromme writes: > > (In other words: PAE might enable you to use RAM >=3D 4 GB, > > but your processes will still be limited to 32bit address > > space.) > > Thanks for the pointer. > That is a good reason to go AMD64 if one has apps which will require lots > of RAM, although I can't think of any program I use ever needing 4GB+ for= a > single program. Well, part of the 4GB+ (1GB at least) is used for the kernel on i386, and part of the space is reserved for stack, etc. such that your effective mmap() limit is more like 2gb IIRC. If a process wanted to mmap a file bigger than 2gb (such as the backing store for a large SQL database) it would have to include its own memory mapper to only mmap a window of the file at a time, etc. With a larger virtual address space it can mmap the entire file without a problem. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org