From: Dan Malek <dan@embeddededge.com>
To: acurtis@onz.com
Cc: gopi@india.tejasnetworks.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: mpc 8260 performance..
Date: Fri, 31 Jan 2003 12:45:52 -0500 [thread overview]
Message-ID: <3E3AB650.5080108@embeddededge.com> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFKEKKEBAA.acurtis@onz.com
Allen Curtis wrote:
> gopi wrote:
>>In this case, the system can potentially be interrupted too...
> Sounds like a HW design issue you need to address. Perhaps it would be
> better to interrupt on buffer full ....
High performance routers don't interrupt at all, typically have
carefully hand-tuned algorithms to maximize the use of processor cache
for instructions and ensure the data bus is aligned and bursting data.
Linux has been used in such designs, but the network drivers are
written specific to those applications. The Linux network drivers are
examples of workstation connections and network layer interfaces, but
aren't suitable for these specialty applications. They are suitable
for functional testing, but not for high performance routing.
An 8260 can process lots of communication data, obviously its performance
is totally dependent upon the software design and implemetation.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-31 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 8:40 mpc 8260 performance gopi
2003-01-31 13:39 ` Allen Curtis
2003-01-31 14:22 ` gopi
2003-01-31 14:33 ` Allen Curtis
2003-01-31 15:13 ` gopi
2003-01-31 15:37 ` Allen Curtis
2003-01-31 17:45 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-31 14:49 Steven Blakeslee
2003-01-31 14:47 ` Allen Curtis
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=3E3AB650.5080108@embeddededge.com \
--to=dan@embeddededge.com \
--cc=acurtis@onz.com \
--cc=gopi@india.tejasnetworks.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).