Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Conﬁguring a System

Reconﬁguring the Kernel (Prior to HP-UX 11i Version 2)

Chapter 3292

DLKM Module Packaging The DLKM infrastructure speciﬁes that:

• a kernel module must be packaged modularly with at least:

— its own master and system ﬁles

— its own mod.o object ﬁle that implements only that module

• the mod.o object ﬁle must contain the Module Wrapper code

(although full optimization is optional).

Dynamically

conﬁgured Loadable

Module

A Dynamically Conﬁgured Loadable Module is a loadable module

which has been fully conﬁgured to be dynamically loaded into or

unloaded from the kernel without having to re-link the entire

kernel or reboot the system.

To summarize the terminology presented in this table, a

Dynamically Conﬁgured Kernel Module is all of the following:

•aModularly packaged Module

(Which is a Kernel Module that uses module-speciﬁc master and

system ﬁles.)

•aLoadable Module (or DLKM Module)

(Which is a Modularly packaged Module that contains the

wrapper code and additional data structures and uses

module-speciﬁc master and system ﬁles, but still could be

conﬁgured as dynamic or statically linked.)

•aDynamically Conﬁgured Loadable Module

(Which is a DLKM Module that has been conﬁgured to be fully

capable of dynamic loading into, and unloading from the

running kernel.

Module Wrapper The additional code and data structures added to a kernel module

which enable the DLKM mechanism to logically connect and

disconnect a loadable module to and from the running kernel.

Table 3-8 Important Terms and Concepts (Continued)

Term / Concept Deﬁnition