mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: Mugunthan V N <mugunthanvnm@ti.com>, Matt Porter <mporter@ti.com>,
	Chase Maupin <chase.maupin@ti.com>, Jason Kridner <jdk@ti.com>,
	Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpsw: Fix interrupt storm among other things
Date: Mon, 28 Jan 2013 20:49:58 +0100	[thread overview]
Message-ID: <20130128194958.GA6129@netboy.at.omicron.at> (raw)
In-Reply-To: <4E26978C-0B09-4E06-8373-49F1850C08C4@antoniou-consulting.com>

On Mon, Jan 28, 2013 at 08:40:25PM +0200, Pantelis Antoniou wrote:
> Hi Richard,
> 
> Yes, I guess this was more of a drive-by patch dump - but people need this
> to get PG2.0 silicon to work on am33xx.

And what is PG2.0?

> And no, I don't think having a non-NAPI code path is backwards, especially
> when trying to debug hardware problems; the non-NAPI driver is much easier
> to understand and follow, especially when there is a convoluted method
> you have to follow to have the h/w acknowledge the interrupt.

Special debug modes are fine to have, but not in mainline code. 
I suggest taking a look at the recent netdev discussion on this.
Someone wanted to make napi/non-napi a DT option, and it got
nixed.

> Not every device can be conveniently be made to shut up so that NAPI processing 
> can take place at a later time.

So, are you saying that the cpsw cannot work as a napi device?
 
> The NAPI case is still broken in this driver, which OOPs under load.

And does your patch fix it, or not?

It would be nice to know what the problem is, and how to reproduce
it. I haven't seen any OOPs on the beaglebone, but maybe I am not
trying hard enough.

Thanks,
Richard

  reply	other threads:[~2013-01-28 19:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 13:11 Pantelis Antoniou
2013-01-28 18:24 ` Richard Cochran
2013-01-28 18:40   ` Pantelis Antoniou
2013-01-28 19:49     ` Richard Cochran [this message]
2013-01-28 19:56     ` Richard Cochran
2013-01-28 18:27 ` Richard Cochran
2013-01-28 21:14 ` Peter Korsgaard
2013-01-30  8:34   ` Pantelis Antoniou
2013-01-29 11:45 ` Mugunthan V N
2013-01-30  8:36   ` Pantelis Antoniou
2013-01-30  9:03     ` Mugunthan V N
2013-01-30  9:36       ` Pantelis Antoniou
2013-01-30 10:55         ` Mugunthan V N
2013-01-30 11:08           ` Pantelis Antoniou
2013-01-30 12:38             ` Bedia, Vaibhav
2013-01-30 12:44               ` Pantelis Antoniou
2013-01-30 13:29                 ` Bedia, Vaibhav
2013-01-30 13:37                   ` Pantelis Antoniou
2013-01-30 13:47                     ` Bedia, Vaibhav
2013-01-30 13:51                       ` Pantelis Antoniou
2013-01-30 13:53                         ` Mugunthan V N
2013-01-30 13:55                           ` Pantelis Antoniou
2013-01-30 14:03                             ` Mugunthan V N
2013-01-30 19:27                             ` Mugunthan V N

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=20130128194958.GA6129@netboy.at.omicron.at \
    --to=richardcochran@gmail.com \
    --cc=chase.maupin@ti.com \
    --cc=jdk@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mporter@ti.com \
    --cc=mugunthanvnm@ti.com \
    --cc=panto@antoniou-consulting.com \
    --cc=tony@atomide.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

all inboxes | Powered by JetHome®