netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mugunthan V N <mugunthanvnm@ti.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: [net PATCH 1/1] drivers: net: cpsw: dual_emac: fix reducing of rx descriptor during ifdown
Date: Wed, 3 Sep 2014 12:46:55 +0530	[thread overview]
Message-ID: <5406C067.5080103@ti.com> (raw)
In-Reply-To: <20140902.115434.1276391011837651390.davem@davemloft.net>

David

On Wednesday 03 September 2014 12:24 AM, David Miller wrote:
> From: Mugunthan V N <mugunthanvnm@ti.com>
> Date: Tue, 2 Sep 2014 14:51:05 +0530
> 
>> When ifup and ifdown is run continuously, for each spilled packet (for
>> interface which is down) from DMA, the total number of rx descriptor
>> goes down and at one instance all the descriptor is lost and both the
>> interface stops working.
>>
>> To recover from this we need to put down both the interface and open the
>> interface which will re-init the DMA which intern queues fresh set of
>> skbs for rx.
> 
> But you still should not receive packets for a netdev which is down.
> As far as I can tell, you're feeding it into the stack still.

If there is separate DMA for each netdev, then it is true that there
won't be a packet for a closed netdev. But in CPSW dual EMAC case, one
DMA engine is shared between two slave ports, so when one slave netdev
is put down, the DMA is not teared down as the other slave netdev is
still active. In heavy traffic network when putting down netdev, there
are chances that packets are already processed by DMA, and waiting for
NAPI to be submitted to network stack might belong to the netdev which
is already down.

So instead of just freeing the skb received on netdev which is already
down (which will reduce the total rx descriptors in rx dma channel),
requeue it back to DMA and make sure that rx dma descriptor count is
never reduced.

> 
> Also this doesn't explain why the "status < 0" case applies to this
> new logic, you have not explained that at all.
> 

This scenario is not generated when "status < 0", "status < 0" happens
when DMA is in tear-down mode, the above scenario happens when
netif_running(ndev) is false which denotes that netdev is down already.

Regards
Mugunthan V N

  reply	other threads:[~2014-09-03  7:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  9:22 [net PATCH 1/1] drivers: net: cpsw: dual_emac: fix reducing of rx descriptor during ifdown Mugunthan V N
2014-09-02  1:31 ` David Miller
2014-09-02  9:21   ` Mugunthan V N
2014-09-02 18:54     ` David Miller
2014-09-03  7:16       ` Mugunthan V N [this message]
2014-09-03 17:07         ` Mugunthan V N
2014-09-05 21:29         ` 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=5406C067.5080103@ti.com \
    --to=mugunthanvnm@ti.com \
    --cc=davem@davemloft.net \
    --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).