Messages in this thread | | | Date | Wed, 15 Jan 2003 04:31:47 -0300 | From | Werner Almesberger <> | Subject | Re: [RFC] Migrating net/sched to new module interface |
| |
kuznet@ms2.inr.ac.ru wrote: > Somewhat overdone.
I think it would be nice to introduce in 2.7 a shutdowncall (*) function class for modules that works like exitcall, but with the following differences:
- does not return before the module has really de-registered itself everywhere, including synchronization with any callbacks, etc. - has a return code, and can fail if it would have to sleep for a possibly long time
Before calling the shutdown function, all symbols exported by the module are hidden, and after the shutdown functions returns, the module can be unloaded.
That way, the module reference count becomes merely advisory information, and the real locking, synchronization, etc. is inside the module.
The module unload mechanism could then check whether the module is old (uses exitcall) or new (uses shutdowncall), and act accordingly. Modules and the services they use could then be gradually fixed.
(*) Or maybe use a nicer name :-)
- Werner
-- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net / /_http://www.almesberger.net/____________________________________________/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |