But wouldn't a bit flag require continuous retries on the part of whomever gets the -EAGAIN when they try to submit an URB? And, if so, wouldn't that leave open the possibility of them missing the window when the BUSY bit isn't set (unless they retry in a very tight loop, in which case they could waste a lot of processor time)?
I've not actually seen a patch for 2.6 implementing any of this. But if you want synchronizing behavior, that's going to mean modifying some subset of the potential blocking paths (can't modify all, there are too many!) ... and leaving holes in the paths you don't modify.
- Dave
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
