> any performance impact, but we have not benchmarked it, either; would > you expect this to make a noticeable difference? no. the cost is trivial: a driver checks its hardware to see whether there really is an interrupt to handle. should take a microsecond or so. > Either way, I would not think the system should lock up completely. of course, if the driver is broken, it won't share an irq correctly. - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
- SMP+Tulip lockup, 2.0.36pre15, help requested Patrick J. LoPresti
- Re: SMP+Tulip lockup, 2.0.36pre15, help request... Kaz Kylheku
- Re: SMP+Tulip lockup, 2.0.36pre15, help req... Patrick J. LoPresti
- Re: SMP+Tulip lockup, 2.0.36pre15, help... Mark Hahn
- Re: SMP+Tulip lockup, 2.0.36pre15, help... Jon Lewis
- Re: SMP+Tulip lockup, 2.0.36pre15, help request... Donald Becker
- Re: SMP+Tulip lockup, 2.0.36pre15, help req... Alan Cox
- Re: SMP+Tulip lockup, 2.0.36pre15, help... Donald Becker
- SMP+eepro lockup, 2.0.35, help requeste... Catherine Charbonnier
- Re: SMP+eepro lockup, 2.0.35, help ... Alan Cox
- Re: SMP+eepro lockup, 2.0.35, ... Catherine Charbonnier
- Re: SMP+eepro lockup, 2.0.... Alan Cox
- Re: SMP+Tulip lockup, 2.0.36pre15, help request... G.W. Wettstein
