From owner-freebsd-current@FreeBSD.ORG Mon May 22 19:17:03 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B7A016AF6C for ; Mon, 22 May 2006 19:17:03 +0000 (UTC) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id A24BA43D49 for ; Mon, 22 May 2006 19:17:02 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.171.127.191] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1FiFtm-000LLJ-1Y; Mon, 22 May 2006 13:17:02 -0600 In-Reply-To: <1e4841eb0605221133s428d9136p3d5f7eff964167f4@mail.gmail.com> References: <1e4841eb0605211854i44c4aa4cm9dfc72506c2232ea@mail.gmail.com> <1e4841eb0605221133s428d9136p3d5f7eff964167f4@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2B495EE0-9E81-4CDD-84AF-D3789C9FCB95@shire.net> Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Mon, 22 May 2006 13:17:01 -0600 To: m m X-Mailer: Apple Mail (2.750) X-SA-Exim-Connect-IP: 67.171.127.191 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Cc: current@freebsd.org Subject: Re: FreeBSD is now self-hosting on the UltraSPARC T1 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: Mon, 22 May 2006 19:17:04 -0000 On May 22, 2006, at 12:33 PM, m m wrote: > On 5/22/06, Chad Leigh -- Shire.Net LLC wrote: >> >> On May 21, 2006, at 7:54 PM, m m wrote: >> >> > While >> > on topic, the Opterons aren't SMP either, and neither are the >> > ht-Xeons... >> >> I would like t\o hear the rational for the Opterons (presumably the >> dual core ones) not being SMP. They have two independent operating >> cores in one physical package. Who cares how it is packaged? I >> would tend to agree with you on the ht-Xeon in terms of general >> descriptions. I do not know as well how the ht-xeon work as I don't >> use any but it seems to me that the "SMP" moniker, at least in >> FreeBSD, relate to how things are scheduled. > > SMP stands for "Symmetric MultiProcessing", which means that multiple > processors have equal access latency to memory - typically > accomplished by sitting the processors on a shared bus with memory. > The MultiProcessor Opterons are _NOT_ SMP, they are _NUMA_ machines, > "NonUniform Memory Access"; in the MP Opterons each processor has (or > can have) its own "local" memory, which makes up only part of the > shared address space. When an Opteron accesses an address that is not > in its "local" memory, it has to talk to a remote processor's memory, > thereby incurring a different access latency. Yes, but until FBSD differentiates and has different code for "SMP" and "NUMA" based systems, then having support for them in the SMP branch seems appropriate. In other words, even if not ideal, if there is no different code, there doesn't need to be a different section for the code. I am no expert, but as far as I can tell, FBSD treats them like an SMP system and the NUMA stuff is done at the HW level. Correct me if I am wrong. Seems like the SMP moniker is a historical one, not a technical one :-) --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net