From: Matt Walters <mattw@parasun.com>
To: netfilter-devel@lists.netfilter.org
Subject: libipq scaling
Date: Wed, 04 Aug 2004 15:30:43 -0700 [thread overview]
Message-ID: <1091658643.32021.91.camel@marx.mindlink.net> (raw)
Hey all-
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.
Has anyone experimented with it? If not, when we do some performance
testing, is anyone interested in the results?
Thanks,
-Matt
next reply other threads:[~2004-08-04 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 22:30 Matt Walters [this message]
2004-08-05 6:31 ` libipq scaling Pablo Neira
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=1091658643.32021.91.camel@marx.mindlink.net \
--to=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.