#1284 closed bug (fixed)
Isochronous finish thread eats up lots of cpu
| Reported by: | jackburton | Owned by: | mmlr |
|---|---|---|---|
| Priority: | high | Milestone: | R1 |
| Component: | Drivers/USB | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Looks like the isochronous finishing thread eats up lots of cpu. Just open processcontroller and you'll see. Maybe it should try to acquire a semaphore before doing anything else (like the other USB finishing thread does).
Change History (3)
comment:1 by , 17 years ago
comment:3 by , 17 years ago
I meant to synchronize somehow the thread, but I didn't know it did cause what it did, otherwise I would done right away. I'm sorry.
Anyway, another possible solution would be to put to sleep the transfer if there are no isochronous transfer, and wake him up as soon as one is submitted.
Note:
See TracTickets
for help on using tickets.
My 2GHz (real hardware) gets so loaded down that it can't be used. The cursor in Terminal blinks once in a while but the keyboard and mice don't work. Not even F12.
Of course I can't verify that it's because of the isochronous finishing thread.