Module parameters on the kernel parameter line
Parameters that the kernel does not recognize as kernel parameters are ignored by the kernel and made available to user space programs.
One of these user space programs is modprobe. modprobe interprets module parameters that are specified on the kernel parameter line if they are qualified with a leading module prefix and a dot.
For example, if the DASD device driver is compiled as a separate
module, you can include a specification with dasd_mod.dasd= on
the kernel parameter line. modprobe evaluates this specification as
the dasd= module parameter when the dasd_mod module
is loaded.
For some device drivers and features, the module
parameters and their corresponding kernel parameters follow a naming
convention that makes them effective regardless of whether the device
driver or feature is compiled into the kernel or as a separate module.
An example is the zfcp.datarouter= kernel parameter
with its corresponding datarouter= module parameter.
If the SCSI-over-Fibre Channel device driver (zfcp
device driver) is compiled into the kernel, zfcp.datarouter= is
recognized as a kernel parameter. If the zfcp device driver is compiled
as a separate module, modprobe interprets zfcp.datarouter= as
the datarouter= parameter to be used when the zfcp module
is loaded.