From: "Robert Iakobashvili" <coroberti@gmail.com>
To: netfilter-devel@lists.netfilter.org
Cc: demiurg@metalinkbb.com
Subject: Re: netfilter performance on low-end embedded systems
Date: Mon, 12 Feb 2007 18:22:12 +0200 [thread overview]
Message-ID: <7e63f56c0702120822v4d4d27cble4d9c07afc40741d@mail.gmail.com> (raw)
Alexander,
> From: Alexander Sirotkin <demiurg@metalinkBB.com>
> I'm trying to evaluate the feasibility of using netfilter on low-end
> embedded processors, such as MIPS 4K or 24K. Basicly what I'm trying to
> understand is whether we can do 100Bps with netfilter enabled (firewall
> and NAT) on such a CPU or should we check hardware acceleration solution.
>
> If anybody did any similar benchmarks and can share results (does not
> have to be on MIPS) or just has any opinion on the subject - I'd be very
> grateful.
With reference to the low-end arm processors, high traffic is not a
problem, unless
you are not using a large number of iptables rules, which traversal by packets
is linear.
If you need lots many rules, e.g. hundreds, thousands, etc, consider
using various
flavors of ipset, nf-hypac, connection tracking, wise rules arrangement, etc.
Sincerely,
Robert Iakobashvili,
coroberti %x40 gmail %x2e com
...................................................................
Navigare necesse est, vivere non est necesse
...................................................................
http://sourceforge.net/projects/curl-loader
A powerful open-source HTTP/S, FTP/S traffic
generating, loading and testing tool.
next reply other threads:[~2007-02-12 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 16:22 Robert Iakobashvili [this message]
2007-02-14 9:31 ` netfilter performance on low-end embedded systems Alexander Sirotkin
-- strict thread matches above, loose matches on Subject: below --
2007-01-10 8:17 Alexander Sirotkin
2007-01-07 13:24 Alexander Sirotkin
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=7e63f56c0702120822v4d4d27cble4d9c07afc40741d@mail.gmail.com \
--to=coroberti@gmail.com \
--cc=demiurg@metalinkbb.com \
--cc=netfilter-devel@lists.netfilter.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).