On 06/17/2015 11:09 AM, Nicolae Rosia wrote: > I'm trying to determine why I have a huge number of IRQs for only a > macb interface and the other one works just fine (low IRQ activity). I > have activated IP forward and I'm just forwarding packets from eth0 to > eth1. > The platform is Zynq7, Linux kernel 4.0, vanilla macb. > > cat /proc/interrupts: > [...] > 144: 679425 0 GIC 54 eth0 > 145: 17867097 0 GIC 77 eth1 > [...] > > Any ideas?
The times we've seen tons of interrupts on Ethernet with interrupts routed through the PL was when the FPGA was unprogrammed (or in the process of being reprogrammed), or was configured with the interrupt line tied to asserted. In the latter case, Linux would eventually stop handling any more interrupts for that port due to the interrupt storm. In the former case, there isn't much one can do except make sure that any FPGA-routed interrupts are unregistered and disabled before FPGA reprogramming and then to re-enable those interrupts after reprogramming. It'd be nice to have some sort of notification to drivers, given when the FPGA state changes, when hardware the drivers are responsible for disappears or gets disconnected. This is an area of research for us at NI. Cheers, Jaeden -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
