From owner-freebsd-stable@FreeBSD.ORG Sat Jul 23 02:53:06 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FC0B16A425 for ; Sat, 23 Jul 2005 02:53:06 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-19-148-33.jan.bellsouth.net [68.19.148.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2279243D46 for ; Sat, 23 Jul 2005 02:53:05 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: by mortis.over-yonder.net (Postfix, from userid 100) id 52C5420FBA; Fri, 22 Jul 2005 21:53:04 -0500 (CDT) Date: Fri, 22 Jul 2005 21:53:03 -0500 From: "Matthew D. Fuller" To: Frank Mayhar Message-ID: <20050723025303.GE32805@over-yonder.net> References: <42E151B4.7030500@bfoz.net> <42E156B2.1070004@exit.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42E156B2.1070004@exit.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Cc: Brandon Fosdick , freebsd-stable@freebsd.org Subject: Re: SMP support maturity? AMD64x2 or FX-57? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jul 2005 02:53:06 -0000 On Fri, Jul 22, 2005 at 01:27:30PM -0700 I heard the voice of Frank Mayhar, and lo! it spake thus: > > Sigh. You know, I've been running with two processors since 4.1 or > thereabouts. Sure, the BGL scheme is inefficient as far as the > kernel itself is concerned, but for compute-bound user processes it > worked just fine. Naturally I avoided 5.0/1/2 for my production > boxen, waiting for the complete overhaul of SMP to stabilize, but > when I booted 5.3, everything was fine and I haven't looked back. This system (this one, right here, that I'm typing on) is dual processor, and I installed it fresh with 4-CURRENT just after RELENG_3 was branched. Except for an excursion on RELENG_5, it's always run -CURRENT. Sometimes I'd go a year without updating, sometimes a week. It's running -CURRENT from a couple weeks ago now. Sometimes it's a bit twitchy, but I think running X has a whole lot to do with that, since MP systems under heavier loads without X would do just peachy with the exact same build that was flaky here. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.