On Wed, 12 Jan 2000, 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.
OS/390 (IBM mainframe operating system) supports 'name/token
pairs'. It supports different scopes, which on a Unix system might
map to names limited to a process or names accessable to all
processes on the system. Associated with the name is a 16 byte
value. It seems to me that a service like this would be the best
way to maintain access to persistant storage across module loads
(with a suitable naming convention). Persistant storage would be
kmalloced, and a pointer to the area saved using a name/token
pair.
Mike
-
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:20 EST