From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo Neira Ayuso Subject: Re: [RFC] ctnetlink events drop benchmark Date: Wed, 14 Jun 2006 14:24:42 +0200 Message-ID: <4490000A.7020500@netfilter.org> References: <448ED2DD.30100@netfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Harald Welte , Netfilter Development Mailinglist , Patrick McHardy Return-path: To: Jozsef Kadlecsik In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org 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