From owner-freebsd-smp Sat Apr 5 07:54:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA13704 for smp-outgoing; Sat, 5 Apr 1997 07:54:21 -0800 (PST) Received: from spinner.DIALix.COM (root@spinner.dialix.com [192.203.228.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA13696 for ; Sat, 5 Apr 1997 07:54:11 -0800 (PST) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.5/8.8.5) with ESMTP id XAA17993; Sat, 5 Apr 1997 23:53:48 +0800 (WST) Message-Id: <199704051553.XAA17993@spinner.DIALix.COM> X-Mailer: exmh version 2.0gamma 1/27/96 To: Doug Rabson cc: smp@freebsd.org Subject: Re: Any chance of sync with current? In-reply-to: Your message of "Sat, 05 Apr 1997 16:37:15 +0100." Date: Sat, 05 Apr 1997 23:53:47 +0800 From: Peter Wemm Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Doug Rabson wrote: > Does anyone know if/when the next sync-with-current thing is going to > happen for the smp tree? I want to try out smp on my new machine (2xP6 on > SuperMicro P6DNE motherboard) but it will be a lot of hassle with the > current smp tree since I need various fixes to the ahc driver from current > to make the machine work at all. I've been thinking about doing it sometime soon, the -current kernel seems to have settled down a fair bit. > On the other hand, what about merging in the other direction SMP->current. > Last time the subject came up, I am sure someone said this would be easier > than merging lite2 and that has already happened... The biggest problem that I can see so far is that we have too many #ifdef's, causing interesting problems like #include "opt_smp.h" to be seen by user programs that #include stuff from . I must have another look again and see how it looks at the moment. It'd be nice to bring it online to the mainstream. > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 951 1891 > Cheers, -Peter