[...]
> Would a patch to add persistent variables for modules be accepted into
> the kernel? Modules define variables like this
>
> static __persistent cache * cache_p;
>
> __persistent in a module stores the data in a separate ELF section,
> when the code is builtin __persistent is a no-op. modutils and
> kernel/modules allocate and initialize storage for __persistent the
> first time the module is loaded. Unloading a module does not remove
> the __persistent data, reloading the module will reuse but not
> initialize the assigned storage.
How large would that be? What about a piece of the module that just stays
put in the kernel (no special section loaded, etc)? If you want this for a
module, you'll probably want to initialize it at boot anyway.
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513- 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/