Alan Cox wrote:
> Add a 'preserved' tag for one section of module memory. On load look up the
> data, if its from this boot memcpy it into the module. On unload write it
> back to disk. No kernel code needed.
I like! No kernel code, yet no races or delay.
As written that removes the possibilities of variable length persistant
data, and the data is opaque to user space.
MODULE_PARM provides type information and structure to the data. Why
not mark certain PARMS as persistent? Not all would be named -- a block
of opaque data is useful. But certain things like all the mixer levels
could be named parameters, giving you both persistant storage _and_
explicit configuration when you want that. "s" PARMS (or similar)
can hold variable length data.
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Nov 15 2000 - 21:00:12 EST