Date: Wed, 14 Jun 2000 03:59:40 -0600 From: Warner Losh <imp@village.org> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: Matthew Dillon <dillon@apollo.backplane.com>, Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>, hackers@FreeBSD.ORG Subject: Re: kerneld for FreeBSD Message-ID: <200006140959.DAA20067@harmony.village.org> In-Reply-To: Your message of "Wed, 07 Jun 2000 08:07:07 EDT." <Pine.NEB.3.96L.1000607075658.25263A-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1000607075658.25263A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm only going to reply once to this thread In message <Pine.NEB.3.96L.1000607075658.25263A-100000@fledge.watson.org> Robert Watson writes: : And in a sense, we already have two kerneld's -- pccardd and usbd, which : maintain mappings between named devices and drivers, etc. Combining them, : and adding another source of requests (and LPC channel over a UNIX domain : socket) would not be that hard. I personally think that a devd would be great to have. One that could do things when devices arrive and leave as well as when the removable hardware/software detects a new hunk of hardware that doesn't attach to any resident driver. It would be extremely useful if only the specific driver that was for that hardware wound up in the kernel. It would also be useful if that module were unloaded when that removable device went away. No need to keep it in memory, so long as there was a way to bring it back later. Sure, there's a monster bug in the kldload/unload right now where that eats wired memory. That bug should be fixed. Finally, all of this would be less of an issue if one could page the kernel, or at least parts of it... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006140959.DAA20067>