that's intra subsystem synchronisation, not inter subsystem
I'd say that device_driver.remove() calls from the bus management code to a given device driver are inter-subsystem...
so using a subsystem provided API from another subsystem constitutes inter subsytem synchronisation? I don't think so.
So it's now "I won't listen to those facts, they bother me" ... Or maybe you're just trolling? "From another subsystem" is "between subsystems" is "inter-subsystem"; Q.E.D.
Either way, it's not worth the time to respond to you any more, this will be my last post on this thread.
Refcounting systems need loop-breaking protocols ("disconnect"); this is needed for that sort of reason, if no other.
No, they don't.
Without protocols for breaking referencing loops, systems that use refcounting _alone_ (as you're advocating) leak memory unless they prevent such loops ... but requests sent from one subsystem to the next, then later returned, each embed such a loop.
That's in addition to the need for locking in certain paths, on multi-threaded systems (like Linux).
(And for that matter, there were no WMDs in Iraq.)
Sorry for mentioning all those inconvenient facts; I'll go away now.
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
