From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Dave Liu <daveliu@freescale.com>
Cc: linuxppc-dev@ozlabs.org, David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: ucc_geth: Fix the wrong the Rx/Tx FIFO size
Date: Thu, 10 Dec 2009 02:00:15 +0300 [thread overview]
Message-ID: <20091209230015.GA13654@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1259309803-5474-1-git-send-email-daveliu@freescale.com>
On Fri, Nov 27, 2009 at 04:16:43PM +0800, Dave Liu wrote:
> current the Rx/Tx FIFO size settings cause problem
> when four UEC ethernets work simultaneously.
>
> eg: GETH1, UEM-J15, GETH2, UEC-J5 on 8569MDS board
>
> $ ifconfig eth0 10.193.20.166
> $ ifconfig eth1 10.193.20.167
> $ ifconfig eth2 10.193.20.168
> then
> $ ifconfig eth3 10.193.20.169
>
> The fourth ethernet will cause all of interface broken,
> you cann't ping successfully any more.
> The patch fix this issue for MPC8569 Rev1.0 and Rev2.0
>
> Signed-off-by: Dave Liu <daveliu@freescale.com>
Acked-by: Anton Vorontsov <avorontsov@ru.mvista.com>
Thanks Dave! I see that the new values actually match the QEIWRM
spec (except UTFS... spec recommends 2048, but it also says that
it might differ for different memory setups, though that's a
separate issue).
And FWIW, I did some quick netperf tests on MPC8360, and the
patch doesn't cause any problems.
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-12-09 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 8:16 ucc_geth: Fix the wrong the Rx/Tx FIFO size Dave Liu
2009-12-09 23:00 ` Anton Vorontsov [this message]
2010-01-04 3:42 ` Liu Dave-R63238
2010-01-04 5:06 ` 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=20091209230015.GA13654@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=daveliu@freescale.com \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.org \
--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).