From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Mark Huth <mhuth@mvista.com>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
Li Yang <leoli@freescale.com>, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] ucc_geth: Fix half-duplex operation for non-MII/RMII interfaces
Date: Thu, 25 Jun 2009 15:17:25 +0400 [thread overview]
Message-ID: <20090625111725.GA30165@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20090625070236.GA27711@oksana.dev.rtsoft.ru>
On Thu, Jun 25, 2009 at 11:02:36AM +0400, Anton Vorontsov wrote:
[...]
> Of course, it could be that the root cause of the problems
> I observe is weird NIC on my host. Well, then QA team should
> have used the same broken NIC on their hosts. :-)
>
> I can easily test it by interconnecting two targets though.
[...]
> Definitely. Though I'm out of ideas if it's NOT host-side issue.
Two boards interconnected work fine. eTSEC + SKY2 NIC also work
OK. I'll test some more NICs, known to not work is 3Com
Corporation 3c905C-TX/TX-M [Tornado] (rev 74).
After some netperf tests, statistic on a gianfar board:
# ethtool -S eth0 | grep -v ": 0"
NIC statistics:
rx-dropped-by-kernel: 2
tx-rx-64-frames: 52
tx-rx-65-127-frames: 20668
tx-rx-128-255-frames: 10343
tx-rx-256-511-frames: 113
tx-rx-512-1023-frames: 147
tx-rx-1024-1518-frames: 45965
rx-bytes: 45075782
rx-packets: 50300
rx-carrier-sense-error: 1
rx-fragmented-frames: 7600
tx-byte-counter: 27401677
tx-packets: 34618
tx-broadcast-packets: 3
tx-deferral-packets: 5
tx-single-collision-packets: 4039
tx-multiple-collision-packets: 1943
tx-excessive-collision-packets: 30
tx-total-collision: 785
Thanks for the ideas, Mark.
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
WARNING: multiple messages have this Message-ID (diff)
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Mark Huth <mhuth@mvista.com>
Cc: David Miller <davem@davemloft.net>,
Kumar Gala <galak@kernel.crashing.org>,
Li Yang <leoli@freescale.com>,
linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH] ucc_geth: Fix half-duplex operation for non-MII/RMII interfaces
Date: Thu, 25 Jun 2009 15:17:25 +0400 [thread overview]
Message-ID: <20090625111725.GA30165@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20090625070236.GA27711@oksana.dev.rtsoft.ru>
On Thu, Jun 25, 2009 at 11:02:36AM +0400, Anton Vorontsov wrote:
[...]
> Of course, it could be that the root cause of the problems
> I observe is weird NIC on my host. Well, then QA team should
> have used the same broken NIC on their hosts. :-)
>
> I can easily test it by interconnecting two targets though.
[...]
> Definitely. Though I'm out of ideas if it's NOT host-side issue.
Two boards interconnected work fine. eTSEC + SKY2 NIC also work
OK. I'll test some more NICs, known to not work is 3Com
Corporation 3c905C-TX/TX-M [Tornado] (rev 74).
After some netperf tests, statistic on a gianfar board:
# ethtool -S eth0 | grep -v ": 0"
NIC statistics:
rx-dropped-by-kernel: 2
tx-rx-64-frames: 52
tx-rx-65-127-frames: 20668
tx-rx-128-255-frames: 10343
tx-rx-256-511-frames: 113
tx-rx-512-1023-frames: 147
tx-rx-1024-1518-frames: 45965
rx-bytes: 45075782
rx-packets: 50300
rx-carrier-sense-error: 1
rx-fragmented-frames: 7600
tx-byte-counter: 27401677
tx-packets: 34618
tx-broadcast-packets: 3
tx-deferral-packets: 5
tx-single-collision-packets: 4039
tx-multiple-collision-packets: 1943
tx-excessive-collision-packets: 30
tx-total-collision: 785
Thanks for the ideas, Mark.
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-06-25 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 17:45 [PATCH] ucc_geth: Fix half-duplex operation for non-MII/RMII interfaces Anton Vorontsov
2009-06-25 5:11 ` Mark Huth
2009-06-25 5:11 ` Mark Huth
2009-06-25 7:02 ` Anton Vorontsov
2009-06-25 7:02 ` Anton Vorontsov
2009-06-25 11:17 ` Anton Vorontsov [this message]
2009-06-25 11:17 ` Anton Vorontsov
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=20090625111725.GA30165@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=davem@davemloft.net \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mhuth@mvista.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.