David Woodhouse <[EMAIL PROTECTED]> writes:
> The current situation is equivalent to stopping forwarding packets each
> time an app on the local machine decides it wants to send its own packets,
> after a period of inactivity.
>
> Defaulting to zero on boot is fine. Defaulting to zero after the module
> has been auto-unloaded and auto-loaded again is less good.
Well we don't have auto unload.
And module persistent data for the second load case causes chaos with
the goal of having exactly the same code in modules and compiled in
kernel code.
It would probably be better (in this case) to increment the module count
when the mixer settings go above 0, and decrement it when the settings
go totally to 0. This prevents an unwanted unload.
But for reliability and code simplicity there does not yet seem to
be a case for persistent module storage.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
