Messages in this thread | | | Date | Wed, 9 Dec 1998 17:20:43 +0100 (CET) | From | Andrea Arcangeli <> | Subject | Re: 2.1.131-ac3 3c509 no irq_save in the sender code |
| |
On Wed, 9 Dec 1998, Alan Cox wrote:
>> to run while the TX is on the fly. But to do that we don' t need the >> spin_lock in el3_interrupt, update_stats will just spin on the lock itself >> if needed. And disable_irq() just synchronize_irqs itself btw (I was wrong >> in my last email). > >You need the lock to protect update stats being called by user space >(eg cat /proc/net/dev) during an IRQ on the other processor or you have >a similar pattern of accidents with the read fifo pulling data out of the >stats buffer
Ah, OK...
Andrea Arcangeli
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |