From owner-freebsd-smp Mon Dec 2 12:30:07 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11030 for smp-outgoing; Mon, 2 Dec 1996 12:30:07 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA11024; Mon, 2 Dec 1996 12:30:05 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.8.3/8.7.3) with ESMTP id OAA04003; Mon, 2 Dec 1996 14:27:38 -0600 (CST) Message-Id: <199612022027.OAA04003@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: Steve Passe cc: Peter Wemm , freebsd-smp@freefall.freebsd.org Subject: Re: cvs commit: sys/i386/include pmap.h In-reply-to: Your message of Mon, 02 Dec 1996 12:23:44 -0700. <199612021923.MAA22076@clem.systemsix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Dec 1996 14:27:38 -0600 From: Chris Csanady Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I think as a first step in the merging of SMP with -current we might >add the line: #include "opt_smp" to every file that now contains SMP code, >At that point everyone would have a good idea of where we will be >affecting the -current tree. > >We probably should also document all SMP specific options in conf/LINT. Sounds good. Although, as we progress, this may be almost all the files in /sys. I was hoping to start moving the locking out into the syscalls. >The next step would be to break up files that have grown to have alot >of SMP stuff mixed with standard stuff, eg. init_main.c -> init_main.c & >init_smp.c. Stated another way, I think we should strive to keep SMP changes >localized to SMP specific files to the extent that it is practical. For now perhaps. But wouldn't the end goal be to have the UP instance just 1 processor SMP case? Im thinking that this would make the code cleaner, and more generic in the end. I think having kernel threads would be well worth it. --Chris Csanady >We also need to think thru the locations of some things b4 the merge: > > does "options SMP" belong in sys/i386/conf/options.i386 or sys/conf/options? > "options APIC_IO" probably does, can options from options be mixed with > options in options.i386, ie can SMP be in one, APIC_IO in the other, and > have them both end up in "opt_smp"? > >We need to start collecting docs, should that be in: src/share/doc, >which would be outside of sys, or should we creat sys/SMP/doc, or ??? > >We also need an SMP specific 'utility' directory for things like mptable.c, >sys/SMP/util perhaps? >-- >Steve Passe | powered by >smp@csn.net | FreeBSD >