From: Brian Kuschak <bkuschak@yahoo.com>
To: "Vladimir A. Gurevich" <vag@paulidav.org>
Cc: linuxppc-embedded@lists.linuxppc.org, linuxppc@opqua.com
Subject: Re: routing performance w/embedded linux on ppc?
Date: Mon, 1 Dec 2003 11:08:28 -0800 (PST) [thread overview]
Message-ID: <20031201190828.20157.qmail@web40911.mail.yahoo.com> (raw)
In-Reply-To: <3FC59BAE.3020801@paulidav.org>
Hi Vlad,
>
> 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/
>
Yes, it looks interesting! I'm glad this is being
introduced as a mechanism for all drivers to use.
I haven't had time to study it in detail, but I'm a
little concerned about NAPI using the softirq context.
In the 2.4 kernels I've seen various performance
issues related to ksoftirqd. Perhaps this has been
fixed in 2.6...
> > 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,
Yes, an important point.
-Brian
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-01 19:08 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
2003-12-01 19:08 ` Brian Kuschak [this message]
[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=20031201190828.20157.qmail@web40911.mail.yahoo.com \
--to=bkuschak@yahoo.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=linuxppc@opqua.com \
--cc=vag@paulidav.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.