All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Matt Walters <mattw@parasun.com>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: libipq scaling
Date: Thu, 05 Aug 2004 08:31:37 +0200	[thread overview]
Message-ID: <4111D449.8080806@eurodev.net> (raw)
In-Reply-To: <1091658643.32021.91.camel@marx.mindlink.net>

Hi Matt,

Matt Walters wrote:

>	We're considering using netfilter to do some packet filtering/tagging
>based on external information, and it seems like libipq is the best way
>to do it.  I'm wondering if there are any issues with using this tool in
>an environment where sustained 30Mbit/s throughput is to be expected. 
>The target platform is a dual Xeon 2.8 with gobs of memory, 2.6.7
>kernel.
>  
>

I think that it will work fine with 30 Mbit/s.

>	Has anyone experimented with it?
>

I don't think so AFAIK. I've been benchmarking netlink sockets which is 
the method used but libipq to pass information from/to user space.

>  If not, when we do some performance testing, is anyone interested in the results?
>  
>
I didn't test libipq performance, but I suppose that it won't work for 
gigabit networks because of netlink sockets limitations. If you do those 
performance testings, please post the results to the mailling list.

To do the testing, I propose you to set three boxes, a client and a 
server with iperf and a box between both of them with libipq enqueuing 
all the packets for a 100Mbit/s network.

regards,
Pablo

  reply	other threads:[~2004-08-05  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 22:30 libipq scaling Matt Walters
2004-08-05  6:31 ` Pablo Neira [this message]
2004-08-05 20:08   ` Matt Walters

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=4111D449.8080806@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=mattw@parasun.com \
    --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.