Date: Wed, 02 Dec 1998 17:45:34 -0800 From: Mike Smith <mike@smith.net.au> To: Richard Wackerbarth <rkw@nomad.dataplex.net> Cc: Mike Smith <mike@smith.net.au>, freebsd-current@FreeBSD.ORG Subject: Re: KLD - what's the idea? Message-ID: <199812030145.RAA02736@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 02 Dec 1998 19:34:29 CST." <Pine.BSF.4.05.9812021924270.1405-100000@nomad.dataplex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Wed, 2 Dec 1998, Mike Smith wrote: > > > > > What are the (rough) plans for this mechanism? > > > > > > > > Convert the entire kernel into an aggregation of KLD modules. Stick > > > > them together in interesting and versatile ways (eg. at build time to > > > > create a monolithic kernel, or at runtime to load/unload drivers, etc.). > > > > > > ... unload probe/init code when it is no longer needed. > > > > This is actually almost totally farcial; the only modules for which > > unloading probe/init code makes any sense are ISA drivers, and even > > then only ISA drivers that don't support PCCARDs. In every other case > > the probe and init code need to be kept around > > Cannot we unload all of the device recognition code once it has done its > job and reload it each time the PCCARD finds a new arrival? What "device recognition code"? If we keep the current model, it's all in a user-space application. If we were to move the CIS ID : driver/rules match code into the kernel, it would be so small and trivial that the effort involved in loading/unloading it would be disproportionate to the space regained (maybe 1 page). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812030145.RAA02736>