From owner-freebsd-smp Mon Apr 28 10:44:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA27163 for smp-outgoing; Mon, 28 Apr 1997 10:44:37 -0700 (PDT) Received: from uhf.wdc.net (uhf.wdc.net [198.147.74.44]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA27149 for ; Mon, 28 Apr 1997 10:44:33 -0700 (PDT) Received: from localhost (bad@localhost) by uhf.wdc.net (8.8.5/8.6.12) with SMTP id NAA01788; Mon, 28 Apr 1997 13:44:13 -0400 (EDT) Date: Mon, 28 Apr 1997 13:44:12 -0400 (EDT) From: Bernie Doehner To: Terry Lambert cc: smp@freebsd.org Subject: Re: Quad Pro 150 motherboard? In-Reply-To: <199704281717.KAA02093@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The PPro's are stackable without additional electronics external > to the processor. This makes it a *lot* easier to do multiple > CPU's up to large numbers. Didn't anyone ever notice those neat traces between the CPUs and other devices on the MB? The higher and higher you go in frequency, the shorter and shorter a wavelength becomes and the more and more these traces start to look like antennas. There's a physical limit as to how long these traces can be and this limit also affects how closely you can space CPUs, without setting up a CPU hierarchy. > Personally, I'd like a 32 processor machine; of course, that means > fixing the kernel so that it doesn't bog down on interprocessor > synchronization, starting with the allocation mechanism and a > hierarchical lock manager. And finding a way to build a 3-D motherboard. > My goal would be to have incremental compiles going on in edit sessions > so that when I was done editing, the code was read to run. I hate this > "wait for the compile" BS. > Would that be nice? :) Bernie