From: Wolfram Sang <w.sang@pengutronix.de>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: Bestcomm trouble with NAPI for MPC5200 FEC
Date: Fri, 10 Jul 2009 10:08:30 +0200 [thread overview]
Message-ID: <20090710080830.GA3241@pengutronix.de> (raw)
In-Reply-To: <4A565423.6010207@grandegger.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Hello Wolfgang,
> 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
That's great news. Do you happen to have a scenario which reliably triggers the
problem? Then I could do some testing as well. I haven't seen this on our
boards for quite a while, but I'd like to verify.
> - 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).
+1 for "error handling resets too much"
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-07-10 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 20:33 Bestcomm trouble with NAPI for MPC5200 FEC Wolfgang Grandegger
2009-07-09 21:22 ` Grant Likely
2009-07-10 7:37 ` Wolfgang Grandegger
2009-07-10 9:16 ` Wolfgang Grandegger
2009-07-10 8:08 ` Wolfram Sang [this message]
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=20090710080830.GA3241@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=Linuxppc-dev@ozlabs.org \
--cc=wg@grandegger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.