From: Jeff Garzik <jeff@garzik.org>
To: Karsten Wiese <fzu@wemgehoertderstaat.de>
Cc: linux-kernel@vger.kernel.org, NetDev <netdev@vger.kernel.org>,
Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: [PATCH] r8169: Fix irq masking in rtl8169_interrupt()
Date: Tue, 17 Mar 2009 16:09:37 -0400 [thread overview]
Message-ID: <49C00381.8050207@garzik.org> (raw)
In-Reply-To: <200903171937.53401.fzu@wemgehoertderstaat.de>
Karsten Wiese wrote:
> Only adjust the NAPI bits of the interruptmask, if netif_rx_schedule_prep()
> returns true.
> Without this, I see interrupt storms here using 2.6.29-rcx and 2.6.27.19 and
> device needed rmmod r8169 + modprobe r8169 to start working.
>
> Signed-off-by: Karsten Wiese <fzu@wemgehoertderstaat.de>
> ---
> drivers/net/r8169.c | 9 ++++-----
> 1 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/r8169.c b/drivers/net/r8169.c
> index b347340..0c943ba 100644
> --- a/drivers/net/r8169.c
> +++ b/drivers/net/r8169.c
> @@ -3708,12 +3708,11 @@ static irqreturn_t rtl8169_interrupt(int irq, void *dev_instance)
> rtl8169_check_link_status(dev, tp, ioaddr);
>
> if (status & tp->napi_event) {
> - RTL_W16(IntrMask, tp->intr_event & ~tp->napi_event);
> - tp->intr_mask = ~tp->napi_event;
> -
> - if (likely(netif_rx_schedule_prep(&tp->napi)))
> + if (likely(netif_rx_schedule_prep(&tp->napi))) {
> + RTL_W16(IntrMask, tp->intr_event & ~tp->napi_event);
> + tp->intr_mask = ~tp->napi_event;
> __netif_rx_schedule(&tp->napi);
> - else if (netif_msg_intr(tp)) {
> + } else if (netif_msg_intr(tp)) {
> printk(KERN_INFO "%s: interrupt %04x in poll\n",
FWIW, you should CC net driver patches to netdev@vger.kernel.org, so
that they get tracked in patchworks and handled by the right people.
Jeff
next parent reply other threads:[~2009-03-17 20:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903171937.53401.fzu@wemgehoertderstaat.de>
2009-03-17 20:09 ` Jeff Garzik [this message]
2009-03-17 19:34 [PATCH] r8169: Fix irq masking in rtl8169_interrupt() Karsten Wiese
2009-03-17 22:06 ` Francois Romieu
2009-03-18 1:56 ` Karsten Wiese
2009-03-18 6:40 ` Francois Romieu
2009-03-18 11:59 ` Karsten Wiese
2009-03-18 22:36 ` Francois Romieu
2009-03-19 6:35 ` David Miller
2009-03-19 10:58 ` Karsten Wiese
2009-03-19 22:23 ` Francois Romieu
2009-03-20 1:40 ` Karsten Wiese
2009-03-22 21:16 ` Francois Romieu
2009-03-22 23:53 ` Karsten Wiese
2009-03-23 22:42 ` Francois Romieu
2009-03-24 0:38 ` Karsten Wiese
2009-03-24 13:54 ` Karsten Wiese
2009-03-24 20:18 ` 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=49C00381.8050207@garzik.org \
--to=jeff@garzik.org \
--cc=fzu@wemgehoertderstaat.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).