Date: Sat, 9 Sep 2006 22:12:37 +0800 From: "Howard Su" <howard0su@gmail.com> To: "Robert Watson" <rwatson@freebsd.org> Cc: arch@freebsd.org Subject: Re: Modularize kernel Message-ID: <f126fae00609090712u53a075cai87fe9812d63fdc1a@mail.gmail.com> In-Reply-To: <20060909131907.G84834@fledge.watson.org> References: <f126fae00609062247n62aaf3d7tac8f3980eeb148fb@mail.gmail.com> <20060907.153239.1219861549.imp@bsdimp.com> <f126fae00609071949u79960am7d781b3fca8058b8@mail.gmail.com> <20060908.001045.1683322424.imp@bsdimp.com> <20060909131907.G84834@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/9/06, Robert Watson <rwatson@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f126fae00609090712u53a075cai87fe9812d63fdc1a>