From: Michael Bellion and Thomas Heinz <nf@hipac.org>
To: P@draigbrady.com
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [ANNOUNCE] nf-hipac v0.8 released
Date: Wed, 02 Jul 2003 18:57:32 +0200 [thread overview]
Message-ID: <3F030EFC.7090809@hipac.org> (raw)
In-Reply-To: 3F02EAE2.8050609@draigBrady.com
Hi Pádraig
You wrote:
> I was testing with 64 byte packets (so around 190Kpps). e100 cards at
> least have a handy mode for continually sending a packet as fast as
> possible. Also you can use more than one interface.
Yes, that's true. When we did the performance tests we had in mind to
compare the worst case behaviour of nf-hipac and iptables.
Therefore we designed a ruleset which models the worst case for both
iptables and nf-hipac. Of course, the test environment could have been
tuned a lot more, e.g. udp instead of tcp, FORWARD chain instead of
INPUT, tuned network parameters, more interfaces etc.
Anyway, we prefer independent, more sophisticated performance tests.
>>> # ./readprofile -m /boot/System.map | sort -nr | head -30
>>> 6779 total 0.0047
>>> 4441 default_idle 69.3906
>>> 787 handle_IRQ_event 7.0268
>>> 589 ip_packet_match 1.6733
>>> 433 ipt_do_table 0.6294
>>> 106 eth_type_trans 0.5521
>>> [...]
>
> Confused me too. The system would lock up and start dropping
> packets after 125 rules. I.E. it would linearly degrade
> as more rules were added. I'm guessing there is a fixed
> interrupt overhead that is accounted for
> by default_idle?
Hm, but once the system starts to drop packets ip_packet_match and
ipt_do_table start to dominate the profile, don't they?
Regards,
+-----------------------+----------------------+
| Michael Bellion | Thomas Heinz |
| <mbellion@hipac.org> | <creatix@hipac.org> |
+-----------------------+----------------------+
prev parent reply other threads:[~2003-07-02 16:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 20:48 [ANNOUNCE] nf-hipac v0.8 released Michael Bellion and Thomas Heinz
2003-06-25 21:03 ` Folkert van Heusden
2003-06-25 23:52 ` Thomas Heinz
2003-06-26 13:38 ` Daniel Egger
2003-06-26 14:20 ` Michael Bellion and Thomas Heinz
2003-06-26 14:45 ` Daniel Egger
2003-06-27 6:06 ` Pekka Savola
2003-06-28 20:04 ` Michael Bellion and Thomas Heinz
2003-06-29 6:26 ` Pekka Savola
2003-06-29 7:45 ` Roberto Nibali
2003-06-29 16:26 ` Michael Bellion and Thomas Heinz
2003-07-02 5:30 ` Pekka Savola
2003-07-02 12:26 ` Michael Bellion and Thomas Heinz
2003-07-02 13:08 ` P
2003-07-02 13:48 ` Michael Bellion and Thomas Heinz
2003-07-02 14:23 ` P
2003-07-02 16:57 ` Michael Bellion and Thomas Heinz [this message]
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=3F030EFC.7090809@hipac.org \
--to=nf@hipac.org \
--cc=P@draigbrady.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 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).