From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
To: Frank Li <Frank.Li@freescale.com>
Cc: lznuaa@gmail.com, shawn.guo@linaro.org, B38611@freescale.com,
davem@davemloft.net, linux-arm-kernel@lists.infradead.org,
netdev@vger.kernel.org, s.hauer@pengutronix.de
Subject: Re: [PATCH v3 1/1 net-next] net: fec: add napi support to improve proformance
Date: Thu, 24 Jan 2013 20:33:13 -0800 [thread overview]
Message-ID: <20130125043311.GA4141@ppwaskie-mobl2.amr.corp.intel.com> (raw)
In-Reply-To: <1359077343-8271-1-git-send-email-Frank.Li@freescale.com>
On Fri, Jan 25, 2013 at 09:29:03AM +0800, Frank Li wrote:
[...]
> static void
> +fec_enet_rx_int_enable(struct net_device *ndev, bool enabled)
> +{
> + struct fec_enet_private *fep = netdev_priv(ndev);
> + uint int_events;
> +
> + int_events = readl(fep->hwp + FEC_IMASK);
> + if (enabled)
> + int_events |= FEC_ENET_RXF;
> + else
> + int_events &= ~FEC_ENET_RXF;
> + writel(int_events, fep->hwp + FEC_IMASK);
> +}
You hold your hw_lock when this is called to disable the interrupt, but
not when you re-enable it. See below.
[...]
> @@ -813,7 +831,14 @@ fec_enet_interrupt(int irq, void *dev_id)
>
> if (int_events & FEC_ENET_RXF) {
> ret = IRQ_HANDLED;
> - fec_enet_rx(ndev);
> +
> + spin_lock(&fep->hw_lock);
> + /* Disable the RX interrupt */
> + if (napi_schedule_prep(&fep->napi)) {
> + fec_enet_rx_int_enable(ndev, false);
> + __napi_schedule(&fep->napi);
> + }
> + spin_unlock(&fep->hw_lock);
> }
>
> /* Transmit OK, or non-fatal error. Update the buffer
> @@ -834,7 +859,16 @@ fec_enet_interrupt(int irq, void *dev_id)
> return ret;
> }
>
> -
> +static int fec_enet_rx_napi(struct napi_struct *napi, int budget)
> +{
> + struct net_device *ndev = napi->dev;
> + int pkgs = fec_enet_rx(ndev, budget);
> + if (pkgs < budget) {
> + napi_complete(napi);
> + fec_enet_rx_int_enable(ndev, true);
Here you're not locking when re-enabling, but you do in the disable path.
Also, when you're disabling interrupts above, you're doing that in your
HW interrupt handler, you should be using spin_lock_irqsave()/irq_restore().
Cheers,
-PJ
next prev parent reply other threads:[~2013-01-25 4:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 1:29 [PATCH v3 1/1 net-next] net: fec: add napi support to improve proformance Frank Li
2013-01-25 4:33 ` Waskiewicz Jr, Peter P [this message]
2013-01-25 4:51 ` Frank Li
2013-01-25 22:23 ` Francois Romieu
2013-01-29 5:03 ` Frank Li
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=20130125043311.GA4141@ppwaskie-mobl2.amr.corp.intel.com \
--to=peter.p.waskiewicz.jr@intel.com \
--cc=B38611@freescale.com \
--cc=Frank.Li@freescale.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lznuaa@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.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