|
|
Before DLKMs were available, all kernel modules were linked statically; the modules always remained linked into the kernel. When you wanted to add a new module or remove an existing module, you had to relink the entire kernel and reboot the system for the new kernel configuration to take effect.
A static module is nonloadable. That is, the module always remains linked into the kernel because either it is always required in the system (for example, the boot hard disk driver), or it is used so frequently or consumes so few resources (for example, the user terminal pseudo-device driver) that it is more efficient to keep the module continuously configured. With DLKM, some modules continue to be linked to the kernel in this traditional manner.