On Jan 12, Keith Owens wrote:
> Some modules claim to have a need to maintain persistent data in the
> kernel even when the module is unloaded and reloaded. I can see four
> approaches to fixing this problem, there may be others. Note: this
> only applies to kernel data, it says nothing about maintaining external
> data across reboots.
>
> Comments please.
>
> Options.
>
> (1) Forbid persistent data. "Sorry, the kernel does not support module
> data that retains its value across unload/reload".
>
> (2) For every module that needs persistent data and is configured in,
> compile some module specific variables into the static kernel and
> export them.
>
> (3) Designate persistent variables in the module source, modutils
> handles these variable differently when unloading and reloading a
> module.
>
> (4) Add a kernel service where a module can register arbitrary data and
> find it again during reload.
>
> (5) Any other ideas?
(2a) For every module that needs persistent data and is configured in,
compile a 2nd module which will only keep those specific variables.
no need to compile them into the static kernel...
usually you won't unload module foo_data but only foo,
but if you decide that you won't need foo _and_ it's persistent data
any longer you still have the options to unload foo_data too and thus
free up (reinitialize after reloading) the persistent data space...
Harald
--
All SCSI disks will from now on ___ _____
be required to send an email notice 0--,| /OOOOOOO\
24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
Harald Koenig, \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik // / \\ \
koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:19 EST