From: Jostein Pettersen <jostein.pettersen@westerngeco.com>
To: linuxppc-embedded@ozlabs.org
Subject: Software routing in 8275
Date: Thu, 09 Dec 2004 16:43:41 +0100 [thread overview]
Message-ID: <5.1.0.14.2.20041209153709.02cfa5f8@wgmail3.oslo.eur.slb.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
Hi,
We consider using a MPC8275 running Embedded Linux to route two 100MB/s
Ethernet links in software. The traffic will mostly be incoming on the two
FE links and outgoing on the PCI bus, which is connected to a gigabit
routing chip (can't connect the two FE links to the routing chip directly,
since it only has GE ports).
My question is:
Will the MPC8275 be able to handle 2xFE full speed?
Doing the calculations about bus speeds etc, it looks ok, but I know Linux
does not like high interrupt rates. Is there a rule of thumb about what's
the maximum recommended interrupt rate at a given clock speed?
Hope to hear from you,
Regards
Jostein Pettersen
[-- Attachment #2: Type: text/html, Size: 730 bytes --]
reply other threads:[~2004-12-09 16:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5.1.0.14.2.20041209153709.02cfa5f8@wgmail3.oslo.eur.slb.com \
--to=jostein.pettersen@westerngeco.com \
--cc=linuxppc-embedded@ozlabs.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).