From owner-freebsd-current@FreeBSD.ORG Fri Aug 15 10:49:02 2003 Return-Path: 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 5017037B401; Fri, 15 Aug 2003 10:49:02 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D85F43F93; Fri, 15 Aug 2003 10:49:01 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h7FHmknq000014 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 15 Aug 2003 13:48:47 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h7FHmfL03863; Fri, 15 Aug 2003 13:48:41 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16189.7417.798216.977283@grasshopper.cs.duke.edu> Date: Fri, 15 Aug 2003 13:48:41 -0400 (EDT) To: John Baldwin In-Reply-To: References: <20030814.224014.08945805.imp@bsdimp.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: lchen@briontech.com cc: current@FreeBSD.org cc: "M. Warner Losh" cc: gallatin@cs.duke.edu Subject: Re: Change to kernel+modules build approach X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 15 Aug 2003 17:49:02 -0000 John Baldwin writes: > > No, generic modules would always work with all kernels except for > exceptional cases like PAE (unavoidable, really), and MUTEX_PROFILING > (this is a debugging thing, so ISV's wouldn't need to ship modules > with that turned on). All this would add is the ability to build > modules optimized for your current kernel. If this is not super > desired (which I wouldn't mind), then I think we should take the > modules out of /boot/kernel and put them in /boot/modules or some such. > I do want to get the metadata down to one copy somehow though. YES! YES! I'd be very much in favor of totally decoupling the modules from the kernel. In fact, once we've done that, we can move the kernel back to /kernel where it belongs, and /boot/modules can become /modules ;) BTW, what, exactly, changes size with PAE? Everything? Or would a driver that just used things like busdma, mutexes, interrupts, etc, be OK assuming the busdma interface were made so that they were always 64-bit? Drew