> interrupt_handler() > { > status = readl(dev->status); > if (status & MY_IRQ_DISABLE) > return; Unfortunately on the 8390 the IRQ statud register is on page 0. The code on the other CPU might not be on page 0. That means we can't even safely check if there is an irq pending or clear it down (bad news on ne2k-pci) without getting that lock. That means we have to be able to just block that one irq source to avoid horrible SMP latency problems. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: QUESTION: Network hangs with ... Manfred Spraul
- Re: QUESTION: Network hangs with ... Andrew Morton
- Re: QUESTION: Network hangs with BP6 and 2.4.x kernels,... Alan Cox
- Re: QUESTION: Network hangs with BP6 and 2.4.x ker... Manfred Spraul
- Re: QUESTION: Network hangs with BP6 and 2.4.x... Ingo Molnar
- Re: QUESTION: Network hangs with BP6 and 2... Manfred Spraul
- Re: QUESTION: Network hangs with BP6 a... Ingo Molnar
- Re: QUESTION: Network hangs with BP6 and 2.4.x... Linus Torvalds
- Re: QUESTION: Network hangs with BP6 and 2... Alan Cox
- Re: QUESTION: Network hangs with BP6 a... Linus Torvalds
- Re: QUESTION: Network hangs with ... Alan Cox
- Re: QUESTION: Network hangs with ... Linus Torvalds
- Re: QUESTION: Network hangs with BP6 and 2.4.x... Frank de Lange
- Re: QUESTION: Network hangs with BP6 and 2... Linus Torvalds
- Re: QUESTION: Network hangs with BP6 a... Roeland Th. Jansen
- Latest status of IDE patches from Andre Jeff Nguyen