From: Wolfgang Grandegger <wg@grandegger•com>
To: linuxppc-dev <Linuxppc-dev@ozlabs•org>
Subject: Bestcomm trouble with NAPI for MPC5200 FEC
Date: Thu, 09 Jul 2009 22:33:39 +0200 [thread overview]
Message-ID: <4A565423.6010207@grandegger.com> (raw)
Hello,
I'm currently trying to implement NAPI for the FEC on the MPC5200 to
solve the well known problem, that network packet storms can cause
interrupt flooding, which may totally block the system. The NAPI
implementation, in principle, is straight forward and works
well under normal and moderate network load. It just calls disable_irq()
in the receive interrupt handler to defer packet processing to the NAPI
poll callback, which calls enable_irq() when it has processed all
packets. Unfortunately, under heavy network load (packet storm),
problems show up:
- With DENX 2.4.25, the Bestcomm RX task gets and remains stopped after
a while under additional system load. I have no idea how and when
Bestcom tasks are stopped. In the auto-start mode, the firmware should
poll forever for the next free descriptor block.
- With 2.6.31-rc2, the RFIFO error occurs quickly which does reset the
FEC and Bestcomm (unfortunately, this does trigger an oops because
it's called from the interrupt context, but that's another issue).
I'm realized that working with Bestcomm is a pain :-( but so far I have
little knowledge of the Bestcomm limitations and quirks. Any idea what
might go wrong or how to implement NAPI for that FEC properly.
TIA,
Wolfgang.
next reply other threads:[~2009-07-09 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 20:33 Wolfgang Grandegger [this message]
2009-07-09 21:22 ` Bestcomm trouble with NAPI for MPC5200 FEC Grant Likely
2009-07-10 7:37 ` Wolfgang Grandegger
2009-07-10 9:16 ` Wolfgang Grandegger
2009-07-10 8:08 ` Wolfram Sang
2009-07-10 8:26 ` Wolfgang Grandegger
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=4A565423.6010207@grandegger.com \
--to=wg@grandegger$(echo .)com \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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