From: Bill Davidsen <davidsen@tmr.com>
To: Roberto Nibali <ratz@drugphish.ch>
Cc: "David S. Miller" <davem@redhat.com>,
ak@suse.de, niv@us.ibm.com, linux-kernel@vger.kernel.org,
jamal <hadi@cyberus.ca>
Subject: Re: [ANNOUNCE] NF-HIPAC: High Performance Packet Classification
Date: Mon, 30 Sep 2002 13:36:55 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1020930133306.20863A-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <3D92CCC5.5000206@drugphish.ch>
On Thu, 26 Sep 2002, Roberto Nibali wrote:
> I've done extensive testing in this field trying to achive fast packet
> filtering with a huge set of not ordered rules loaded into the kernel.
>
> According to my findings I had reason to believe that after around 1000
> rules for ipchains and around 4800 rules for iptables the L2 cache was
> the limiting factor (of course given the slowish iptables/conntrack
> table lookup).
>
> Those are rule thresholds I achieved with a PIII Tualatin and 512KB L2
> cache. With a sluggish Celeron with I think 128KB L2 cache I achieved
> about 1/8 of the above treshold. That's why I thought the L2 cache plays
> a bigger role in this than the CPU FSB clock.
>
> I concluded that if the ruleset to be matched would exceed the treshold
> of what can be loaded into the L2 cache we see cache trashing and that's
> why performance goes right to hell. I wanted to test this using oprofile
> but haven't found the correct cpu performance counter yet :).
>
> > Also not necessary, only the top level cache really needs to be
> > top performance.
>
> I will do a new round of testing this weekend for a speech I'll be
> giving. This time I will include ipchains, iptables (of course I am
> willing to apply every interesting patch regarding hash table
> optimisation and whatnot you want me to test), nf-hipac, the OpenBSD pf
> and of course the work done by Jamal.
Look forward to any info you can provide.
I particularly like that nf-hipac can be put in and tried in one-to-one
comparison, that leaves an easy route to testing and getting confidence in
the code.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2002-09-30 17:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D924F9D.C2DCF56A@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <20020925.170336.77023245.davem@redhat.com.suse.lists.linux.kernel>
2002-09-26 0:31 ` [ANNOUNCE] NF-HIPAC: High Performance Packet Classification Andi Kleen
2002-09-26 0:29 ` David S. Miller
2002-09-26 0:46 ` Andi Kleen
2002-09-26 0:44 ` David S. Miller
2002-09-26 9:00 ` Roberto Nibali
2002-09-26 9:06 ` David S. Miller
2002-09-26 9:24 ` Roberto Nibali
2002-09-26 9:21 ` David S. Miller
2002-09-26 15:13 ` James Morris
2002-09-26 20:51 ` Roberto Nibali
2002-09-26 10:25 ` Roberto Nibali
2002-09-26 10:20 ` David S. Miller
2002-09-26 10:49 ` Roberto Nibali
2002-09-26 12:03 ` jamal
2002-09-26 20:23 ` Roberto Nibali
2002-09-27 13:57 ` jamal
2002-09-26 12:04 ` Andi Kleen
2002-09-26 20:49 ` Roberto Nibali
2002-09-30 17:36 ` Bill Davidsen [this message]
2002-10-02 17:37 ` Roberto Nibali
2002-09-26 1:17 ` Nivedita Singhvi
2002-09-26 1:15 ` Andi Kleen
2002-09-26 0:06 Nivedita Singhvi
2002-09-26 0:03 ` David S. Miller
2002-09-26 0:50 ` Nivedita Singhvi
2002-09-26 0:40 ` David S. Miller
2002-09-26 1:09 ` Nivedita Singhvi
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.3.96.1020930133306.20863A-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=niv@us.ibm.com \
--cc=ratz@drugphish.ch \
/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).