From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: FEC ERROR 41200000 on CLLF-860T
Date: Sun, 12 Dec 1999 20:25:55 -0500 [thread overview]
Message-ID: <38544B23.24E35D4B@netx4.com> (raw)
In-Reply-To: 19991212235604.AF1D4F4E5@elph.research.canon.com.au
Graham Stoney wrote:
> Marcus is right;
My apologies.
> ....... Can anyone elaborate or provide pointers to more
> information on the FEC throughput issue? Is there really a hardware problem in
> the CPU, or is it a board specific issue?
The FEC must transfer data at the Ethernet rate because it doesn't
have enough FIFO for an entire packet (it has some clever
optimizations for collision and retrasmit). The SDMA is always
to system memory, so if the buffers are there, the bits will fly.
It all comes down to what your application is doing, and if
the PPC core has enough computes to provide buffers at the
rate you require. I am sure I can write a demo application
that will run at the maximum rate, and maybe it will represent
what you are trying to accomplish......I am working on it.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-13 1:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-07 6:41 FEC ERROR 41200000 on CLLF-860T Graham Stoney
1999-12-07 6:54 ` Dan Malek
1999-12-07 7:05 ` Graham Stoney
1999-12-07 17:23 ` Dan Malek
1999-12-09 0:24 ` Graham Stoney
1999-12-09 11:18 ` Marcus Sundberg
1999-12-09 18:11 ` Dan Malek
1999-12-10 12:39 ` Marcus Sundberg
1999-12-12 23:56 ` Graham Stoney
1999-12-13 1:25 ` Dan Malek [this message]
1999-12-15 16:20 ` Marcus Sundberg
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=38544B23.24E35D4B@netx4.com \
--to=dan@netx4.com \
--cc=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
--cc=greyham@research.canon.com.au \
--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).