Skip to contentSkip to conversation

Is an alternative module interface needed/possible?

RFC Adam J. Richter 3 participants 3 messages Feb 20, 2003

lore
Share & tools
lore
#0 lore raw
Quoted 11 lines · Roman Zippel
Quoted 4 lines · Adam J. Richter

The ability to remove a module is generally independent of
whether or not there is any hardware present at that moment for which the module supplies a driver. Instead, the determining issue is whether there are file descriptors open for that driver.

I don't understand, what you're trying to say.
File descriptors are not the only way to access a driver and the ability to remove a module is only dependent on the number of references to this module.

You're right. My second sentence was an oversimplification.
I should have said "software references" rather than file descriptors to include things like "ifconfig eth0 up" creating a reference, mounting a block device creating a refernece, etc. (Perhaps I should have stated only my first sentence and stopped there.)

Anyhow, my point is that removing a piece of hardware
does not require that the corresponding module be unloaded immediately.

Adam J. Richter     __     ______________   575 Oroville Road
[email protected]     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America

"Free Software For The Rest Of Us."

#1 lore raw
Quoted 3 lines · Adam J. Richter

Anyhow, my point is that removing a piece of hardware
does not require that the corresponding module be unloaded immediately.

Nor does the use of a module require the presence of any non-generic hardware in the first place (e.g. net/sched/, netfilter, PPP, etc.) :-)

- Werner

Signature · 3 lines
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         [email protected] /
/_http://www.almesberger.net/____________________________________________/
#2 lore raw
In reply to Adam J. Richter

Hi,

Quoted 3 lines · Adam J. Richter

Anyhow, my point is that removing a piece of hardware
does not require that the corresponding module be unloaded immediately.

That's true, but when a piece of hardware is removed, you usually also want to get rid of some data structures, but if the relevant functions are not prepared to be called outside of module_exit, you have a huge problem.

bye, Roman