From owner-freebsd-current@FreeBSD.ORG Wed Jun 6 16:41:48 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9908D16A41F for ; Wed, 6 Jun 2007 16:41:48 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.freebsd.org (Postfix) with ESMTP id 6A89C13C45A for ; Wed, 6 Jun 2007 16:41:48 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 06 Jun 2007 09:08:15 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.13.1/8.12.11) with ESMTP id l56GCnbk097590; Wed, 6 Jun 2007 09:12:49 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.13.1/8.13.1/Submit) id l56GCnYc097589; Wed, 6 Jun 2007 09:12:49 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200706061612.l56GCnYc097589@ambrisko.com> In-Reply-To: <86ps49l5pc.fsf@dwp.des.no> To: =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= Date: Wed, 6 Jun 2007 09:12:49 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: jroberson@chesapeake.net, freebsd-current@freebsd.org, almarrie@gmail.com Subject: Re: Intel C2D COREs not used equally in FreeBSD 7.0-CURRENT i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2007 16:41:48 -0000 Dag-Erling Sm\xc3\xb8rgrav writes: | Oliver Fromme writes: | > It's a common mistake to assume that amd64 only makes sense | > if you have >= 4GB RAM. There are several reasons why it | > might be useful to switch from i386 to amd64: | > | > - Most programs (though not all) will run faster, because | > in amd64 mode there are twice as many general-purpose | > registers, giving compilers much better opportunities | > for optimizations and caching of values, and reducing | > slow memory accesses. | | "twice as many" is an understatement. AMD64 has 16 GPRs vs i386's 8 if | you consider BP, SI, DI and SP as GPRs (as the AMD and Intel literature | does); in practical terms the score is 12 to 4. | | > - Some applications might benefit from a larger virtual | > address space > 4 GB. (Note that this is not related | > to the amount of physical RAM!) | | For instance, Varnish maps its entire storage into memory, and will | benefit greatly from the increased address space. | | > In practice there's (almost) only one reason not to run | > FreeBSD/amd64 on amd64-capable hardware: If you depend | > on a certain piece of software which is known not to run | > correctly in 64bit mode. Fortunately those are not many. | | The only one I can think of (for a desktop) is the Flash plugin. Why? With the nspluginwrapper we can running Linux Flash in a FreeBSD native browser on amd64 or i386. With the appropriate compile foo or probably by getting a Linux compiled version it would work with a Linux browser. Nspluginwrapper is great for running i386 plugins on amd64! The only thing that is preventing me from running full time on an amd64 kernel is the kernel support for suspend & resume. I had to add a small hack the kernel to let the i386 Xserver to run on amd64. I need to do some more digging to answer some questions that alc had. Personally, I want to run amd64 full time so I can run and build amd64 and i386 things on my laptop without rebooting at native speed. Doug A.