Am Dienstag, 21. September 2004 17:07 schrieb Alan Stern:
> The fact is, a driver for a hot-pluggable bus needs to guarantee that
> certain operations will be serialized: probe, disconnect, suspend, resume,
> add child, remove child. �To do this requires locking either the
> individual device during these events (as usbcore now does) or locking
> _every_ device in the driver model (as dpm_sem does). �This would work --
> slowly perhaps, but without deadlock -- if dpm_sem were locked uniformly
> whenever one of these events occurs, but it isn't.
>
> In the end, it may turn out to be necessary for the entire driver model to
> adopt the form of locking that usbcore now uses, or something very similar
> to it.
IMHO USB is the unusual case because it is a bus and a tree. A
generic locking model probably has to lock the whole bus. Or of course,
on a higher level. Is there enough contention that a global lock would
be impractical?
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
