From: Kevin Fry <kevin@carts.com>
To: linuxppc emb3dd3d list <linuxppc-embedded@lists.linuxppc.org>
Subject: 8260 Communications Proccessor overload??
Date: Tue, 09 Oct 2001 20:09:59 -0700 [thread overview]
Message-ID: <3BC3BC07.D6158215@carts.com> (raw)
Has anyone ever run all 3 FCC ports at the same time with a
100Mbit link? I think I'm seeing the Communications Processor get
overloaded, but Motorola claims there is no problem. The setup is as
follows: FCC1 is ftp-ing a very large file out (say 100MBytes). FCC2
is
ftp-ing a very large file in. FCC3 is being pinged at maximum rate by a
PC.
What happens occasionally (like 1 out of 10 times) is that
the ping on FCC3 is not responded to in any manner. A close examination
of
the Ethernet PHY (AM79C874) indicates no errors, but the MAC is
reporting
CRC errors. I have captured the MAC --> PHY transfers on a logic
analyzer
and am decoding them at present (I hate computing a CRC-32 by hand). I
was
hoping someone else has experience relative to this situation.
Thanks,
Kevin Fry
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-10-10 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 3:09 Kevin Fry [this message]
2001-10-10 18:02 ` 8260 Communications Proccessor overload?? Dan Malek
2001-10-11 18:11 ` Trevor Coolidge
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=3BC3BC07.D6158215@carts.com \
--to=kevin@carts.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).