Messages in this thread | | | Date | Wed, 07 Mar 2001 23:53:34 +1100 | From | Andrew Morton <> | Subject | Re: spinlock help |
| |
"Hen, Shmulik" wrote: > > The kdb trace was accurate, we could actually see the e100 ISR pop from no > where right in the middle of our ans_notify every time the TX queue would > fill up. When we commented out the call to spin_*_irqsave(), it worked fine > under heavy stress for days. > > Is it possible it was something wrong with 2.4.0-test10 specifically ? >
Sorry, no. If spin_lock_irqsave()/spin_unlock_irqrestore() were accidentally reenabling interrupts then it would be the biggest, ugliest catastrophe since someone put out a kernel which forgot to flush dirty inodes to disk :)
Conceivably it was a compiler bug. Were you using egcs-1.1.2/x86?
- - 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/
| |