Am Montag, 17. März 2003 21:09 schrieb David Brownell:
You know, in all this email I think one of the key issues has somehow not gotten brought out: the need to let the I/O requests get canceled when the task gets signaled. Or at least having an option to do that.
You mean signalled as in Ctrl-C?
Or "kill -TERM" etc. Keyboard interrupts aren't the only signals.
In what regard don't we support that? We have no general connection of URBs with tasks, at least not in all cases.
By definition, there is such an association in any synchronous call, since only tasks may sleep.
We don't support that since all the synchronous calls currently use TASK_UNINTERRUPTIBLE. So signals will be ignored during the "I/O wait".
What's wrong with using the fine macros provided in 2.5 to sleep with TASK_INTERRUPTIBLE and unlink in the interruption case?
The current synchronous calls force TASK_UNINTERRUPTIBLE, and I don't know what macros you're talking about that would do all that. Is there some other synchronous API for urbs, about which I'm unaware?
- Dave
Regards Oliver
------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
