From: Alexander Duyck <alexander.h.duyck@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Nicolas Schichan <nschichan@freebox.fr>
Cc: "David S. Miller" <davem@davemloft.net>,
Tobias Klauser <tklauser@distanz.ch>, Felipe Balbi <balbi@ti.com>,
Wilfried Klaebe <w-lkml@lebenslange-mailadresse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcm63xx_enet: fix poll callback.
Date: Tue, 03 Mar 2015 08:09:19 -0800 [thread overview]
Message-ID: <54F5DCAF.9070102@redhat.com> (raw)
In-Reply-To: <1425390142.5130.173.camel@edumazet-glaptop2.roam.corp.google.com>
On 03/03/2015 05:42 AM, Eric Dumazet wrote:
> On Tue, 2015-03-03 at 05:29 -0800, Eric Dumazet wrote:
>> On Tue, 2015-03-03 at 12:45 +0100, Nicolas Schichan wrote:
>>> In case there was some tx buffer reclaimed and not enough rx packets
>>> to consume the whole budget, napi_complete would not be called and
>>> interrupts would be kept disabled, effectively resulting in the
>>> network core never to call the poll callback again and no rx/tx
>>> interrupts to be fired either.
>>>
>>> Fix that by only accounting the rx work done in the poll callback.
>>>
>>> Signed-off-by: Nicolas Schichan <nschichan@freebox.fr>
>>> ---
>> This looks better, thanks.
>>
>> Acked-by: Eric Dumazet <edumazet@google.com>
>>
>> Note that the way bcm_enet_tx_reclaim() is written, it can livelock on
>> SMP hosts :
>>
>> CPU 1,2,3,... keep queuing packets via ndo_start_xmit()
>>
>> CPU 0 is looping forever in bcm_enet_tx_reclaim() draining queue and
>> freeing skbs.
>>
>> To avoid that, I would take priv->tx_lock only once, or add a limit on
>> the number of skbs that can be drained per round.
> Something like this (untested) patch
>
> diff --git a/drivers/net/ethernet/broadcom/bcm63xx_enet.c b/drivers/net/ethernet/broadcom/bcm63xx_enet.c
> index 21206d33b638..9e8e83865e52 100644
> --- a/drivers/net/ethernet/broadcom/bcm63xx_enet.c
> +++ b/drivers/net/ethernet/broadcom/bcm63xx_enet.c
> @@ -429,29 +429,23 @@ static int bcm_enet_receive_queue(struct net_device *dev, int budget)
> */
> static int bcm_enet_tx_reclaim(struct net_device *dev, int force)
> {
> - struct bcm_enet_priv *priv;
> - int released;
> + struct bcm_enet_priv *priv = netdev_priv(dev);
> + int released = 0;
>
> - priv = netdev_priv(dev);
> - released = 0;
> + spin_lock(&priv->tx_lock);
>
> while (priv->tx_desc_count < priv->tx_ring_size) {
> struct bcm_enet_desc *desc;
> struct sk_buff *skb;
>
> - /* We run in a bh and fight against start_xmit, which
> - * is called with bh disabled */
> - spin_lock(&priv->tx_lock);
> -
> desc = &priv->tx_desc_cpu[priv->tx_dirty_desc];
>
> - if (!force && (desc->len_stat & DMADESC_OWNER_MASK)) {
> - spin_unlock(&priv->tx_lock);
> + if (!force && (desc->len_stat & DMADESC_OWNER_MASK))
> break;
> - }
>
> /* ensure other field of the descriptor were not read
> - * before we checked ownership */
> + * before we checked ownership
> + */
> rmb();
>
This rmb() can probably be replaced with a dma_rmb() since it is just a
coherent/coherent ordering you are concerned with based on the comment.
- Alex
next prev parent reply other threads:[~2015-03-03 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 11:45 [PATCH] bcm63xx_enet: fix poll callback Nicolas Schichan
2015-03-03 13:29 ` Eric Dumazet
2015-03-03 13:42 ` Eric Dumazet
2015-03-03 13:53 ` Nicolas Schichan
2015-03-03 14:18 ` Eric Dumazet
2015-03-03 14:43 ` Nicolas Schichan
2015-03-03 17:42 ` Florian Fainelli
2015-03-03 23:05 ` Jonas Gorski
2015-03-03 16:09 ` Alexander Duyck [this message]
2015-03-03 16:32 ` Eric Dumazet
2015-03-04 20:45 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2015-03-02 17:28 Nicolas Schichan
2015-03-03 3:15 ` David Miller
2015-03-03 11:18 ` Nicolas Schichan
2015-03-03 19:03 ` David Miller
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=54F5DCAF.9070102@redhat.com \
--to=alexander.h.duyck@redhat.com \
--cc=balbi@ti.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nschichan@freebox.fr \
--cc=tklauser@distanz.ch \
--cc=w-lkml@lebenslange-mailadresse.de \
/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).