Re: Testers wanted: exorcised kmod.c: no more daemon!

Russell Kroll (rkroll@exploits.org)
Tue, 14 Apr 1998 00:11:39 -0600


> unloaded explicitely and immediately. Making modules *not* auto-unload
> by default would solve many of the "my mixer settings aren't saved"
> problems, too. I'm curious to know peoples thoughts on this matter.

Losing the auto-unload would break at least one aspect of my setup, unless
some method of saying "I'm done, take it out" from userspace was
available. Specifically, I use the auto-unload feature to crank out the
bttv module when done using the card, since having it loaded blocks out
the "passthrough" audio port on the board.

For my setup, the module could be removed when the device closes out, and
everything would be happy. Unfortunately I suspect this won't be
agreeable to other people that may open and close a device a lot, and
expect rapid responses without the latency of reloading and unloading
every time.

Perhaps some sort of "linger" hint could be specified at insmod time?
This way something like bttv could disappear when the last process exits
(when the use count hits 0) and other modules could stick around for
a while.

Standard "two cents" comment applies.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu