From owner-freebsd-current@FreeBSD.ORG Wed Aug 20 00:53:59 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 B9E2416A4BF; Wed, 20 Aug 2003 00:53:59 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0603D43F93; Wed, 20 Aug 2003 00:53:57 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc1fj.dialup.mindspring.com ([209.86.5.243] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19pNmx-0004qZ-00; Wed, 20 Aug 2003 00:53:52 -0700 Message-ID: <3F4328D8.962337F3@mindspring.com> Date: Wed, 20 Aug 2003 00:52:56 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Watson References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4c89e7a6cb520b347bc3a571e641048fc3ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: Mark Sergeant cc: freebsd-current@freebsd.org Subject: Re: Broken kernel compile on 5.1-RELEASE / 5-CURRENT (SMP, PAE &scsi) 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: Wed, 20 Aug 2003 07:54:00 -0000 Robert Watson wrote: > Can't speak to the specifics of this, but you want to be very careful not > to use kernel modules with PAE: modules are currently without the context > of the kernel configuration file, and PAE introduces possible binary > incompatibility with modules that dig into VM (which many drivers do). This is a good argument for defining it as it's own port, like IA64 or SPARC or whatever. > Various > conversations have happened regarding how to address this problem, and I'm > not sure we've come up with the right answer yet. There seem to be two > conflicting directions: build modules in the context of a kernel module > (and get conditionally compiled type/structure/code/... pieces), and try > to make the module build entirely independent of a kernel configuration. The approach I prefer is: PAE gives you access to up to 64G of real memory, and you really only use it when you have more than 4G of physical memory (my understanding of the memory architecture on the hardware where this would be used is that the minimum ends up being 6G). So you should have no objection to compiling all the drivers in statically, since it's not like you need to save the space. 8-) 8-). -- Terry