> > True, but relvant only for irq handlers.
> 
> So you agree that it might make sense to move uhci_irq to a tasklet, since 
> it _is_ an IRQ handler?

Absolutely. Sorry about being unclear about that.

[..]
> >From the point of view of enqueue, the other code is dequeue and uhci_irq.  
> >From the point of view of uhci_irq, the other code is enqueue and dequeue.  
> None of the three runs in process context, in general.
> 
> Using spin_lock_bh() in enqueue or dequeue isn't a solution because 
> existing code already calls these routines with interrupts disabled.

How so? If you convert the irq code to a tasklet, it'll run in a tasklet.

        Regards
                Oliver


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to