On Sun, Dec 09, 2001 at 12:51:01AM +0100, Martin Diehl wrote:
> On Mon, 3 Dec 2001, Pete Zaitcev wrote:
> 
> > [checking urb->status]
> > 
> > The thread that checks for the status may get a signal and
> > be awaken before callback is called, but after status was set.
> > In that case something oopses: either the thread, or the HCA
> > interrupt.
> 
> Am I right when believing we would need some per-urb "callback completed"
> flag? I mean the drv->can_read approach doesn't work with a pool of urbs 
> to read from? What about adding "atomic_t urb->completed"?

I usually shuffle them between lists in such cases - that way
a working thread does not need to scan, looking for flags.
Not a big deal in USB, but suppose you have 5,500 SCSI requests...

-- Pete

_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to