From owner-freebsd-arch@FreeBSD.ORG Sat Sep 9 14:12:38 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD99016A407 for ; Sat, 9 Sep 2006 14:12:38 +0000 (UTC) (envelope-from howard0su@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62E7243D49 for ; Sat, 9 Sep 2006 14:12:38 +0000 (GMT) (envelope-from howard0su@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so1212331pye for ; Sat, 09 Sep 2006 07:12:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GDkVpIj6ux+mC8/9Qo2fu15S7pwG0yDgj/bz0NMl6pIw5jO4V6/2XhCR8X4HA0TzoR4uXR0ILUKqZW7fffDxsBsai4/bbTWP102Pibww1UvJwoHFVx8Mm186ZCzNwL4RlqIgXLuFA7BZ2Ood6f7rcPvlGYfpHRR2qiEhTNXpCtQ= Received: by 10.35.18.4 with SMTP id v4mr4984919pyi; Sat, 09 Sep 2006 07:12:37 -0700 (PDT) Received: by 10.35.44.12 with HTTP; Sat, 9 Sep 2006 07:12:37 -0700 (PDT) Message-ID: Date: Sat, 9 Sep 2006 22:12:37 +0800 From: "Howard Su" To: "Robert Watson" In-Reply-To: <20060909131907.G84834@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060907.153239.1219861549.imp@bsdimp.com> <20060908.001045.1683322424.imp@bsdimp.com> <20060909131907.G84834@fledge.watson.org> Cc: arch@freebsd.org Subject: Re: Modularize kernel X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Sep 2006 14:12:38 -0000 On 9/9/06, Robert Watson wrote: > > On Fri, 8 Sep 2006, M. Warner Losh wrote: > One of the biggest concerns I have with moving towards a heavily modularized > default kernel is that we may find we need to explore improving our automatic > loading of modules. For example, if we want to de-populate the base kernel > with respect to device drivers, which take up quite a lot of space, we'll want > to look both at how to handle early boot, and later loading if hardware turns > up -- issues we've largely avoided by virtue of compiling them in. We may, > for example, want to look at Apple's approach of loading all the available > modules sequentially early in the boot to see what attachs, unload the idle > modules, and then provide demand loading later. How about you can add one entry into TODO list with some clarification to encourage some volunteers to work on it. -- -Howard