netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>,
	linux-kernel@codethink.co.uk, netdev@vger.kernel.org,
	nobuhiro.iwamatsu.yj@renesas.com, magnus.damm@opensource.se,
	cm-hiep@jinso.co.jp
Subject: Re: [RFC/PATCH v3] sh_eth: use RNC mode for packet reception
Date: Wed, 4 Jun 2014 10:26:56 +0900	[thread overview]
Message-ID: <20140604012656.GE25936@verge.net.au> (raw)
In-Reply-To: <538E685A.1000505@renesas.com>

On Wed, Jun 04, 2014 at 09:29:14AM +0900, Yoshihiro Shimoda wrote:
> Hi Ben,
> 
> (2014/06/03 20:21), Ben Dooks wrote:
> > 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
> > 
> > Since feedback from Yoshihiro Shimoda shows that every supported LSI
> > for this driver should have the bit enabled it seems the best way is
> > to remove the RMCR default value from the per-system data and just
> > write it when initialising the RMCR value. This is discussed in
> > the message (http://www.spinics.net/lists/netdev/msg284912.html).
> > 
> > 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>
> 
> Thank you very much for the patch.
> 
> Acked-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>

If this patch is fine by Shimoda-san then its fine be me too.

Acked-by: Simon Horman <horms+renesas@verge.net.au>

  reply	other threads:[~2014-06-04  1:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 11:21 [RFC/PATCH v3] sh_eth: use RNC mode for packet reception Ben Dooks
2014-06-04  0:29 ` Yoshihiro Shimoda
2014-06-04  1:26   ` Simon Horman [this message]
2014-06-04  2: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=20140604012656.GE25936@verge.net.au \
    --to=horms@verge.net.au \
    --cc=ben.dooks@codethink.co.uk \
    --cc=cm-hiep@jinso.co.jp \
    --cc=linux-kernel@codethink.co.uk \
    --cc=magnus.damm@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).