Why o why?
Posted Jan 29, 2004 12:55 UTC (Thu) by hummassa
In reply to: Module unloading in a reference counted world
Parent article: Module unloading in a reference counted world
I did not understand your arguments. Modules can be shutdown/reinitialized without unloading. So, let's see:
- To reinitialise hardware without rebooting... shutdown module, reinitialize module, no need to unload.
- Hot-pluggable hardware (including PCMCIA and USB), especially on laptops that are suspended rather than being rebooted and that sometimes use a vast number of different hot-pluggable devices between reboots... vast number? let's see... I have two different 802.11b usb adapters + mp3 player + camera + webcam + mouse + keyboard + palmtop + flash disk + smart media reader. All of them take, like, 100KiB of the kernel memory? the hotplug routine is (at boot): verify all hotplugable stuff if they are still there, if not send hotplug-unplug event to the driver, it sits there until you want to plug the thing on again.
- Rarely used filesystems on removable media (e.g. accessing an HFS CD-ROM)... why not just leave it there?
Ok, before you start hating me, I will give the only real good argumento pro-module-unloading: so you can upgrade a buggy or insecure module without (possibly expensive in terms of time) rebooting the machine.
to post comments)