From: "Allen Curtis" <acurtis@onz.com>
To: <gopi@india.tejasnetworks.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: mpc 8260 performance..
Date: Fri, 31 Jan 2003 06:33:55 -0800 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFIEKHEBAA.acurtis@onz.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0301311412001.21680-100000@localhost.localdomain>
> interfaces: hdlc interfaces (external hdlc controller connected
> to 8260 which
> can write to SDRAM directly. Hence 8260 wont be
> involved in packet copying).
>
> routing:
> +------------+
> Ethernet | 8260 based |hdlc
> External world <===========> | embedded |----- 40 systems
> | system |-----
> | |-----
> +------------+
>
> As you can see, the systems on hdlc are connected to external world
> through the 8260 based embedded system.
>
> At peak, 8260 will have to get/send of all the hdlc interfaces and
> route them to external world over Ethernet.
The only processor overhead you should have is inspecting the HDLC packets
and repackaging them for routing purposes. Take some time and learn the
Ethernet and SKB portions of Linux. You should be able to preallocate all
your buffers. The HDLC ASIC will DMA into RAM, the 8260 will DMA out the
Ethernet packets. Achievable CPU utilization should be very low.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-31 14:33 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 [this message]
2003-01-31 15:13 ` gopi
2003-01-31 15:37 ` Allen Curtis
2003-01-31 17:45 ` Dan Malek
-- 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=NCBBIINEHIPFGJPLBEIFIEKHEBAA.acurtis@onz.com \
--to=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).