[lkml]   [2000]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectPersistent module storage - modutils design
Enough people have asked for persistent module storage to at least
justify me writing the code. The design is simple.

MODULE_PARM(var,type) currently defines type as [min[-max]]{b,h,i,l,s}.
For persistent data support, type is now [min[-max]]{b,h,i,l,s}{p}, the
trailing 'p' for persistent is optional. Existing modutils only checks
one character after [min[-max]] so this is backwards compatible, no
need to upgrade modutils unless you want persistent data.

insmod takes parameters from modules.conf, from the saved persistent
data (see below) and from the command line, in that order. The last
value for a parameter takes precedence.

rmmod locates the object for the module using the __insmod_xxx_O ksyms
entry. If the object cannot be found or its timestamp has changed
since it was loaded then rmmod silently skips the persistent data.
Otherwise rmmod uses the .modinfo data in that object to determine the
address and type of the persistent parameters. Each persistent
parameter is extracted from the module being unloaded, formatted as a
module parameter (e.g. "irq=17") and written to /somewhere/module_name
which is a text file (vi is the ultimate configuration tool).

Almost all support is in user space. The only kernel change is to add
'p' to the end of module parameters that are to be persistent. Module
variables that are to be persistent and are not currently module
parameters need to be defined as MODULE_PARM(). The same kernel code
should work on 2.2 and 2.4 kernels, it should even work with modutils

I have not decided where to save the persistent module parameters. It
could be under /lib/modules/<version>/persist or it could be under
/var/log or /var/run. I am tending towards /var/run/module_persist, in
any case it will be a modules.conf parameter.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:45    [W:0.209 / U:0.452 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site