I've followed the thread on "Persistent module
storage" but haven't come across a general explanation
of the changes to the inter-module symbol stuff
between 2.4test10 and test11. Anyone care to comment
on the differences or on whether this is going to be a
stable API for 2.4 (it won't be changed again)?
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
On Fri, 1 Dec 2000 10:52:35 -0800 (PST),
Al Peat <[email protected]> wrote:
> I've followed the thread on "Persistent module
>storage" but haven't come across a general explanation
>of the changes to the inter-module symbol stuff
>between 2.4test10 and test11. Anyone care to comment
>on the differences or on whether this is going to be a
>stable API for 2.4 (it won't be changed again)?
You are confusing two completely different topics. inter_module_xxx
replaced get_module_symbol because the latter was a bad interface, it
violated module layering and broke when symbol versions were turned on.
inter_module_xxx is clean and stable, it has also been sent to Alan Cox
for inclusion in 2.2 kernels, although 2.2 will still have
get_module_symbol for backwards compatibility.
Persistent module data is the ability to save module parameters at
unload time. It only makes sense for parameters that are changed by
users after load, e.g. volume controls, TV tuner settings etc. That
facility is almost completely in user space and requires very few
changes to modules. Watch this space.