From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Steve Bergman <steve@rueb.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Performance of iptables-restore on large rule sets
Date: Fri, 28 Jan 2005 20:19:07 +0100 [thread overview]
Message-ID: <1106939947.1085.13.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <41FA8ADE.6080708@rueb.com>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On Fri, 2005-01-28 at 12:56 -0600, Steve Bergman wrote:
> I have a large rule set (~53000 rules) that I sometimes load using
> iptables-restore. (It takes almost an hour.
>
> Googling around tells me that the loop detection code in the kernel is
> slow with large rule sets. The only thing that seems odd to me is that
> throughout the entire loading process, iptables-restore is consistently
> at about 67% user and33% system processor time according to vmstat. If
> the slowness is in the kernel, shouldn't I be seeing a high and ever
> increasing amount of "system" time?
The loop checking takes place in userspace.
> Kernel is 2.6.9-1.681_FC3. Iptables is iptables-1.2.11-3.1.FC3.
Please try what is going to be released as iptables 1.3.0
You can get the latest snapshot here:
ftp://ftp.netfilter.org/pub/iptables/snapshot/iptables-1.3.0-20050127.tar.bz2
Read the file called INSTALL to see how to compile and install it. (and
make sure you are actually using the new version after it's installed,
either by using the absolute patch, /usr/local/sbin/iptables or by
uninstalling the iptables rpm)
It contains a rewrite of libiptc which is the library that performs the
ruleset modifications, it's much faster now.
I hope it improves your situation.
--
/Martin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-28 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 18:56 Steve Bergman
2005-01-28 19:19 ` Martin Josefsson [this message]
2005-01-31 23:06 ` Harald Welte
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=1106939947.1085.13.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@rueb.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
all inboxes | Powered by JetHome®