From: David Miller <davem@davemloft.net>
To: ben.dooks@codethink.co.uk
Cc: linux-kernel@codethink.co.uk, netdev@vger.kernel.org,
nobuhiro.iwamatsu.yj@renesas.com, magnus.damn@opensource.se,
horms@verge.net.au, yoshihiro.shimoda.uh@renesas.com,
cm-hiep@jinso.co.jp
Subject: Re: [PATCH v2] sh_eth: use RNC mode for R8A7790/R87791
Date: Mon, 02 Jun 2014 11:53:03 -0700 (PDT) [thread overview]
Message-ID: <20140602.115303.1283021229124256917.davem@davemloft.net> (raw)
In-Reply-To: <1401729456-23514-1-git-send-email-ben.dooks@codethink.co.uk>
From: Ben Dooks <ben.dooks@codethink.co.uk>
Date: Mon, 2 Jun 2014 18:17:36 +0100
> The current behaviour of the sh_eth driver is not to use the RNC bit
> for the receive ring. This means that every packet recieved is not only
> generating an IRQ but it also stops the receive ring DMA as well until
> the driver re-enables it after unloading the packet.
>
> This means that a number of the following errors are generated due to
> the receive packet FIFO overflowing due to nowhere to put packets:
>
> net eth0: Receive FIFO Overflow
>
> I have tested the RMCR_RNC configuration with NFS root filesystem and
> the driver has not failed yet. There are further test reports from
> Sergei Shtylov and others for both the R8A7790 and R8A7791.
>
> There is also feedback fron Cao Minh Hiep[1] which reports the
> same issue in (http://comments.gmane.org/gmane.linux.network/316285)
> showing this fixes issues with losing UDP datagrams under iperf.
>
> Tested-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
Given the description, I can't fathom a reason why this wouldn't be
set always, for every chip.
Do some chips not implement this bit at all?
next prev parent reply other threads:[~2014-06-02 18:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 17:17 [PATCH v2] sh_eth: use RNC mode for R8A7790/R87791 Ben Dooks
2014-06-02 18:53 ` David Miller [this message]
2014-06-02 19:06 ` Ben Dooks
2014-06-02 19:33 ` Sergei Shtylyov
2014-06-02 20:49 ` David Miller
2014-06-02 20:55 ` Sergei Shtylyov
2014-06-02 21:05 ` David Miller
2014-06-02 21:17 ` Sergei Shtylyov
2014-06-02 22:26 ` Sergei Shtylyov
2014-06-03 11:19 ` Ben Dooks
2014-06-03 20:02 ` Sergei Shtylyov
2014-06-03 2:45 ` Yoshihiro Shimoda
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=20140602.115303.1283021229124256917.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ben.dooks@codethink.co.uk \
--cc=cm-hiep@jinso.co.jp \
--cc=horms@verge.net.au \
--cc=linux-kernel@codethink.co.uk \
--cc=magnus.damn@opensource.se \
--cc=netdev@vger.kernel.org \
--cc=nobuhiro.iwamatsu.yj@renesas.com \
--cc=yoshihiro.shimoda.uh@renesas.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).