From: gopi@india.tejasnetworks.com
To: Allen Curtis <acurtis@onz.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: RE: mpc 8260 performance..
Date: Fri, 31 Jan 2003 14:22:15 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.21.0301311412001.21680-100000@localhost.localdomain> (raw)
In-Reply-To: <NCBBIINEHIPFGJPLBEIFKEKDEBAA.acurtis@onz.com>
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.
my main concern was that, at peak, what would be the 8260 resources usage.
hope this clarifies
thanx
gopi
PS: Please note that we are not trying to build a full fledged router.
It is only a means of reaching the right side systems from the
external world.
On Fri, 31 Jan 2003, Allen Curtis wrote:
> > We are planning to use 8260 for our embedded system. One of the
> > job is to do routing of around 40 interfaces, with each interface
> > at about 500Kbps duplex.
>
> What kind of interfaces? What kind of routing?
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-31 14:22 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 [this message]
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
-- 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=Pine.LNX.4.21.0301311412001.21680-100000@localhost.localdomain \
--to=gopi@india.tejasnetworks.com \
--cc=acurtis@onz.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).