From: "Vladimir A. Gurevich" <vag@paulidav.org>
To: Brian Kuschak <bkuschak@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org, linuxppc@opqua.com
Subject: Re: routing performance w/embedded linux on ppc?
Date: Wed, 26 Nov 2003 22:37:34 -0800 [thread overview]
Message-ID: <3FC59BAE.3020801@paulidav.org> (raw)
In-Reply-To: <20031126181826.50858.qmail@web40911.mail.yahoo.com>
Brian Kuschak wrote:
> The performance on 4xx is dependent on how much work
> you want to do in the ethernet driver.
>
> A (nearly) stock kernel will be able to forward 64
> byte packets at around 15,000 pps on 200MHz 405GP.
> The interrupts burn alot of CPU cycles. If you
> implement a timer-based interrupt mitigation scheme
> using the FIT timer interrupt to clean out the RX and
> TX rings, you will be able to hit about 35K to 40K
> pps.
I definitely agree with Brian's numbers and recommendations :)
Just a couple of comments:
Starting with 2.4.19 or so, I'd recommend looking at NAPI to do
interrupt mitigation instead. Please look at
ftp://robur.slu.se/pub/Linux/net-development/NAPI/
> On top of that, you can implement
> CONFIG_NET_FASTROUTE in the driver, bypassing most of
> the IP stack.
But, of course, you'll loose IP tables. Also, CONFIG_NET_FASTROUTE won't
help in case you use a DHCP client (or any other app that uses raw
sockets). This might not be that important for a router but be warned!
Regards,
Vladimir
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-27 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 18:18 routing performance w/embedded linux on ppc? Brian Kuschak
2003-11-27 4:11 ` linuxppc user
2003-11-27 6:37 ` Vladimir A. Gurevich [this message]
2003-12-01 19:08 ` Brian Kuschak
[not found] <F9102D41F595D311ACA7009027DE2C8408EBBA92@c3po.heurikon.com>
2003-11-26 4:21 ` linuxppc user
-- strict thread matches above, loose matches on Subject: below --
2003-11-25 4:18 linuxppc user
2003-11-26 19:18 ` Peter Vandenabeele
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=3FC59BAE.3020801@paulidav.org \
--to=vag@paulidav.org \
--cc=bkuschak@yahoo.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=linuxppc@opqua.com \
/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).