From: "Davey" <daveywu@transengines.com>
To: "Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>
Cc: <larryzheng@transengines.com>
Subject: 405ep ether port broken in performance test.
Date: Wed, 26 May 2004 11:44:21 +0800 [thread overview]
Message-ID: <004f01c442d3$c1d60d60$5500a8c0@davey> (raw)
In-Reply-To: 20040525102352.A1329@home.com
I am developing a firewall based on ibm405ep, it have 4 ether ports, two on-chip and two 8139c. And it run 2.4.18 MontaVista kernel.
Between two on-chip ports, one of a port will be broken after 0-2 seconds when I test the transaction rate with small packet (64 byte). and the port will return to fine 2-5minutes after the test end. When I use big packets, i works very fine. My tool is netiq chariot.
Between on-chip port and 8139c port, the result is fine.
Can anyone give me some help?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-26 3:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 13:12 curious about BK checkin protocol Robert P. J. Day
2004-05-25 17:23 ` Matt Porter
2004-05-26 3:44 ` Davey [this message]
2004-05-26 11:19 ` Robert P. J. Day
2004-05-26 16:57 ` Tom Rini
2004-05-26 17:20 ` Robert P. J. Day
2004-05-26 17:35 ` Matt Porter
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='004f01c442d3$c1d60d60$5500a8c0@davey' \
--to=daveywu@transengines.com \
--cc=larryzheng@transengines.com \
--cc=linuxppc-embedded@lists.linuxppc.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).