Peter Memishian wrote:
> > How about something like this: a new module type could be introduced
> > (e.g. "mac/{ether, ib, ...}"). At MAC driver registration time, the name
> > of the plugin is passed by the driver (e.g. through the m_type_ident
> > field of mac_register_t). The MAC layer can modload() the plugin module
> > at that time, and holds it until the MAC unregisters.
>
> This sounds feasible, and I like the idea of having these be dynamically
> loaded. Unless there aren't issues with this approach that others can
> think of, I'll modify the document to reflect that.
So you'll use mod_hold_by_name() to keep the reference?
I suppose that's one way to do it. What happens if I just do a
modload() and simply keep the module from unloading (I can do that since
I have control of the plugin specific reference count)? Is that
considered in bad taste?
-Seb
_______________________________________________
networking-discuss mailing list
[email protected]
