From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Mark Huth <mhuth@mvista.com>, jgarzik@pobox.com, netdev@vger.kernel.org
Subject: Re: [PATCH] natsemi: netpoll fixes
Date: Tue, 13 Mar 2007 16:45:58 +0300 [thread overview]
Message-ID: <45F6AB16.1090300@ru.mvista.com> (raw)
In-Reply-To: <20070313001442.GD21302@sirena.org.uk>
Hello.
Mark Brown wrote:
> Subject: natsemi: Fix NAPI for interrupt sharing
> The interrupt status register for the natsemi chips is clear on read and
> was read unconditionally from both the interrupt and from the NAPI poll
> routine, meaning that if the interrupt service routine was called (for
> example, due to a shared interrupt) while a NAPI poll was scheduled
> interrupts could be missed. This patch fixes that by ensuring that the
> interrupt status register is only read by the interrupt handler when
> interrupts are enabled from the chip.
>
> It also reverts a workaround for this problem from the netpoll hook and
> improves the trace for interrupt events.
>
> Thanks to Sergei Shtylyov <sshtylyov@ru.mvista.com> for spotting the
> issue, Mark Huth <mhuth@mvista.com> for a simpler method and Simon
> Blake <simon@citylink.co.nz> for testing resources.
> Signed-Off-By: Mark Brown <broonie@sirena.org.uk>
> Index: linux-2.6/drivers/net/natsemi.c
> ===================================================================
> --- linux-2.6.orig/drivers/net/natsemi.c 2007-03-11 02:32:43.000000000 +0000
> +++ linux-2.6/drivers/net/natsemi.c 2007-03-13 00:12:29.000000000 +0000
[...]
> @@ -2131,17 +2133,23 @@
> dev->name, np->intr_status,
> readl(ioaddr + IntrMask));
>
> - if (!np->intr_status)
> - return IRQ_NONE;
> -
> - prefetch(&np->rx_skbuff[np->cur_rx % RX_RING_SIZE]);
> + if (np->intr_status) {
> + prefetch(&np->rx_skbuff[np->cur_rx % RX_RING_SIZE]);
>
> - if (netif_rx_schedule_prep(dev)) {
> /* Disable interrupts and register for poll */
> - natsemi_irq_disable(dev);
> - __netif_rx_schedule(dev);
> + if (netif_rx_schedule_prep(dev)) {
> + natsemi_irq_disable(dev);
> + __netif_rx_schedule(dev);
> + } else
> + printk(KERN_WARNING
> + "%s: Ignoring interrupt, status %#08x, mask %#08x.\n",
> + dev->name, np->intr_status,
> + readl(ioaddr + IntrMask));
> +
> + return IRQ_HANDLED;
> }
> - return IRQ_HANDLED;
> +
> + return IRQ_NONE;
> }
The only "complaint" I have is that this "restructuring" seems
unnecessary: the only real change it does is an addition of else to the if
statement.
WBR, Sergei
next prev parent reply other threads:[~2007-03-13 13:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 20:10 [PATCH] natsemi: netpoll fixes Sergei Shtylyov
2007-03-05 22:41 ` Mark Brown
2007-03-05 22:43 ` Mark Brown
2007-03-06 4:10 ` Mark Huth
2007-03-10 20:25 ` Sergei Shtylyov
2007-03-11 12:16 ` Mark Brown
2007-03-12 13:05 ` Sergei Shtylyov
2007-03-12 19:11 ` Mark Brown
2007-03-13 13:53 ` Sergei Shtylyov
2007-03-13 19:31 ` Mark Brown
2007-03-12 19:12 ` Sergei Shtylyov
2007-03-12 19:05 ` Mark Huth
2007-03-13 0:14 ` Mark Brown
2007-03-13 13:45 ` Sergei Shtylyov [this message]
2007-03-06 11:10 ` Jeff Garzik
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=45F6AB16.1090300@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=broonie@sirena.org.uk \
--cc=jgarzik@pobox.com \
--cc=mhuth@mvista.com \
--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 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).