Messages in this thread | | | Subject | Re: spinlock help | Date | Wed, 7 Mar 2001 13:19:06 +0000 (GMT) | From | Alan Cox <> |
| |
> spin_lock_bh() won't block interrupts and we need them blocked to prevent > more indications. > spin_lock_irq() could do the trick but it's counterpart spin_unlock_irq() > enables all interrupts by calling sti(), and this is even worse for us.
Why dont you queue your indications then. The eepro100 driver doesnt end up with large locked sections so its obviously possible to handle it sanely
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |