Re: Device count (to be done with)

[<Oliver.Neukum@lrz.uni-muenchen.de>]

On Mon, 15 Oct 2001, Stamatis Mitrofanis wrote:
> If I got your idea right, you suggest that:
> - should-count is stored for each kernel module, independent of
> "subsystem" (usb, pci etc.).

Yes, but the subsystem might very well manage the count on behalf of
individual modules.

> - when should-count is decremented to 0, the module is "autoclean".
> - should-count is queried by kernel.

What for ?

> - should-count is incremented/decremented by kernel.
> - should-count is queried by modprobe.
>
> I was suggesting the following:
> - should-count is stored for each kernel module, independent of "subsystem".
> - when should-count is decremented to 0, the module is "autoclean".
> - should-count is queried by kernel.
> - should-count is incremented/decremented by kernel.
> - should-count is queried by modprobe.
> - should-count is incremented/decremented by modprobe.
>
> It's just whether user-space is allowed to increment/decrement the count
> that differs. I believe that there has to be a user-space interface to
> this count since the should-count is abstract (hence not specific to
> PCI, USB or anything) and counts just "reasons for this module to remain
> loaded (not to be autocleaned)" . Thus, user-space may have its own set
> of reasons to have this module loaded in the kernel.

If user space wants that it should implement its own counters or locking
scheme.

> I think we've pretty much settled this issue. So now, the question is
> (again), who's going to write it...

I will do it unless someone volunteers until next week, when I'll have the
time necessary.
Question, by which mechanism should user space be able to query the count
?

	Regards
		Oliver



_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel