From: Jaeden Amero <jaeden.amero@ni.com>
To: Nicolae Rosia <nicolae.rosia@gmail.com>, netdev@vger.kernel.org
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Josh Cartwright <joshc@ni.com>
Subject: Re: macb napi strange behavior
Date: Wed, 17 Jun 2015 13:54:52 -0500 [thread overview]
Message-ID: <5581C27C.4040408@ni.com> (raw)
In-Reply-To: <CAH=tA9FfYh_XSg7y=TujXwuvrjvgg+hOY1j_UOyJNK5mrwaBCw@mail.gmail.com>
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
next prev parent reply other threads:[~2015-06-17 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 16:09 macb napi strange behavior Nicolae Rosia
2015-06-17 18:54 ` Jaeden Amero [this message]
2015-06-17 19:00 ` Nicolae Rosia
2015-06-17 20:20 ` Florian Fainelli
2015-06-20 16:43 ` Francois Romieu
2015-06-22 19:04 ` Nicolae Rosia
2015-06-26 17:50 ` Nicolae Rosia
2015-06-26 23:15 ` Francois Romieu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5581C27C.4040408@ni.com \
--to=jaeden.amero@ni.com \
--cc=cyrille.pitchen@atmel.com \
--cc=joshc@ni.com \
--cc=netdev@vger.kernel.org \
--cc=nicolae.rosia@gmail.com \
--cc=nicolas.ferre@atmel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox