All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: jeff@garzik.org, "netdev" <netdev@vger.kernel.org>
Subject: Re: [PATCH 10/11][TG3]: Reduce spurious interrupts.
Date: Sat, 05 May 2007 17:15:02 -0700	[thread overview]
Message-ID: <1178410502.4859.46.camel@dell> (raw)
In-Reply-To: <20070504.204700.24899658.davem@davemloft.net>

On Fri, 2007-05-04 at 20:47 -0700, David Miller wrote:
> From: "Michael Chan" <mchan@broadcom.com>
> Date: Fri, 4 May 2007 19:50:10 -0700
> 
> > In a small number of cases, we really get a ton of spurious interrupts.
> > We have even seen the kernel shutting off IRQ7 because of too many
> > unclaimed spurious interrupts.
> 
> Ok, that's a big problem.
> 
> In retrospect the read back is only needed on non-MSI
> right?  I guess that'd be ok.
> 
Right, not needed in MSI as MSI is considered an edge interrupt.  I will
resubmit a new patch to just flush the mailbox.


  reply	other threads:[~2007-05-05 23:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05  0:55 [PATCH 10/11][TG3]: Reduce spurious interrupts Michael Chan
2007-05-05  0:42 ` Jeff Garzik
2007-05-05  1:45   ` Michael Chan
2007-05-05  2:42     ` David Miller
2007-05-05  2:50       ` Michael Chan
2007-05-05  3:47         ` David Miller
2007-05-06  0:15           ` Michael Chan [this message]
2007-05-06  0:19           ` [PATCH revised 10/11][TG3]: Eliminate " Michael Chan
2007-05-07  7:26             ` David Miller
2007-05-06  0:21           ` [PATCH revised 11/11][TG3]: Update version and reldate Michael Chan
2007-05-07  7:26             ` David Miller
2007-05-07 16:39         ` [PATCH 10/11][TG3]: Reduce spurious interrupts Rick Jones
     [not found]           ` <1178562469.4859.70.camel@dell>
2007-05-07 17:44             ` Rick Jones
2007-05-07 18:41               ` Michael Chan

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=1178410502.4859.46.camel@dell \
    --to=mchan@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    /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.