Date: Sat, 11 Aug 2001 11:51:49 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: wpaul@freebsd.org (Bill Paul) Cc: green@freebsd.org (Brian F. Feldman), cvs-committers@freebsd.org, cvs-all@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: cvs commit: src/sys/kern link_elf.c Message-ID: <200108110251.LAA20177@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Fri, 10 Aug 2001 16:46:55 MST." <20010810234655.7A24237B401@hub.freebsd.org> References: <20010810234655.7A24237B401@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> I must be misremembering that at one point you couldn't unload a preloaded >> module... > >It was probably due to this bug. :) > >A pre-loaded module looks exactly the same to the system as a module >loaded after system boot. If you pre-load a driver module on which the >system depends, i.e. the driver for the disk controller on which your >root filesystem resides, then you can't unload it without catastrophic >results. But that's a special case. In my case, I'm trying to unload a >driver for a network card which is idle, and it works properly now with >this fix. The only pre-loaded module you can't ever unload under any >circumstances is "kernel." Um, would tell me more about preloaded modules? Is the module text and data image of the preloaded module in the memory space free()ed? I seem to recall it wasn't the case before. So, the physical memory used by a preloaded module remained occupied after this module is unloaded, and never re-used... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108110251.LAA20177>