From: Roberto Nibali <ratz@drugphish.ch>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org, netdev <netdev@oss.sgi.com>
Subject: Re: [ANNOUNCE] NF-HIPAC: High Performance Packet Classification
Date: Wed, 02 Oct 2002 19:37:00 +0200 [thread overview]
Message-ID: <3D9B2EBC.4010102@drugphish.ch> (raw)
In-Reply-To: Pine.LNX.3.96.1020930133306.20863A-100000@gatekeeper.tmr.com
Hi,
>>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.
Unfortunately (as always) there were tons of delays that didn't allow me
to finish the complete test suite as I hoped I could but I sent some
information off this list to Jamal and the nf-hipac guys about previous
test result. See below. I hope I can do more tests this weekend ...
> 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.
Yes and it was very convincing after the first few tests Some prelimiary
test with raw TCP throughput have given me following really cool results:
TCP RAW throughput 100Mbit/s max MTU:
-------------------------------------
ratz@laphish:~/netperf-2.2pl2 > ./netperf -H 192.168.1.141 -p 6666 -l 60
TCP STREAM TEST to 192.168.1.141
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/s
87380 16384 16384 60.01 88.03 <------
ratz@laphish:~/netperf-2.2pl2 >
TCP RAW throughput 100Mbit/s max MTU with 10000 non-matching rules + 1
last matching rule at the end of the FORWARD chain [iptables]:
----------------------------------------------------------------------
ratz@laphish:~/netperf-2.2pl2 > ./netperf -H 192.168.1.141 -p 6666 -l 60
TCP STREAM TEST to 192.168.1.141
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
87380 16384 16384 60.12 3.28 <------
ratz@laphish:~/netperf-2.2pl2 >
TCP RAW throughput 100Mbit/s max MTU with 10000 non-matching rules + 1
last matching rule at the end of the FORWARD chain [nf-hipac]:
----------------------------------------------------------------------
ratz@laphish:~/netperf-2.2pl2 > ./netperf -H 192.168.1.141 -p 6666 -l 60
TCP STREAM TEST to 192.168.1.141
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
87380 16384 16384 60.03 85.78 <------
ratz@laphish:~/netperf-2.2pl2 >
For nf-hipac I also have some statistics:
-----------------------------------------
bloodyhell:/var/FWTEST/nf-hipac # cat /proc/net/nf-hipac
nf-hipac statistics
-------------------
Maximum available memory: 65308672 bytes
Currently used memory: 1764160 bytes
INPUT:
- INPUT chain is empty
FORWARD:
- Number of rules: 10002
- Total size: 1033010 bytes
- Total size (allocated): 1764160 bytes
- Termrule size: 80016 bytes
- Termrule size (allocated): 320064 bytes
- Number of btrees: 30007
* number of u32 btrees: 10003
+ distribution of u32 btrees:
[ 2, 4]: 10002
[ 16384, 32768]: 1
* number of u16 btrees: 10002
+ distribution of u16 btrees:
[ 1, 2]: 10002
* number of u8 btrees: 10002
+ distribution of u8 btrees:
[ 2, 4]: 18
OUTPUT:
- OUTPUT chain is empty
bloodyhell:/var/FWTEST/nf-hipac #
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
next prev parent reply other threads:[~2002-10-02 17:31 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
2002-10-02 17:37 ` Roberto Nibali [this message]
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=3D9B2EBC.4010102@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 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.