Hi Dave, I think this one > * Removes driver->serialize ... not needed, since > it's only gotten when the bus writelock is held.
is problematic for efficiency reasons: suppose I want to protect myself from (for example) configuration changes. By taking dev->serialize I am taking a per-device lock, so in the common case when the core is not changing configurations, lock contention only occurs with other processes using the same device. But if I have to take the bus lock, then contention is with all processes using that bus. For that matter, if dev->serialize was a rwsem, then contention could be reduced even further. Duncan. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
