From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [RFC] ctnetlink events drop benchmark
Date: Wed, 14 Jun 2006 14:24:42 +0200 [thread overview]
Message-ID: <4490000A.7020500@netfilter.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0606141002490.32191@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> On Wed, 14 Jun 2006, Jozsef Kadlecsik wrote:
>
>>Can we generalize your results and state that (ct)netlink can handle (on
>>the given hardvare) max 500-1000 messages/s?
>
> Oops, that's false: 500-1000 NEW messages/s. But what is the total number
> of messages/s?
Actually, my concern wasn't really to get the messages/s rate. I started
the benchmark to know if ctnetlink can back off under big stress
situation, in other words, if I could experiment messages loss. This is
really important to validate conntrackd. And it could also be for other
subsystems like nfqueue.
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
next prev parent reply other threads:[~2006-06-14 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 14:59 [RFC] ctnetlink events drop benchmark Pablo Neira Ayuso
2006-06-14 7:44 ` Jozsef Kadlecsik
2006-06-14 8:04 ` Jozsef Kadlecsik
2006-06-14 12:24 ` Pablo Neira Ayuso [this message]
2006-06-14 11:38 ` Pablo Neira Ayuso
2006-06-14 13:55 ` Patrick McHardy
2006-06-14 16:39 ` Pablo Neira Ayuso
2006-06-14 18:36 ` Patrick McHardy
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=4490000A.7020500@netfilter.org \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=laforge@netfilter.org \
--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 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.