From: Patrick McHardy <kaber@trash.net>
To: Thomas Jacob <jacob@internet24.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Further speedup of iptables when modifying an existing ruleset
Date: Wed, 02 Jul 2008 12:27:32 +0200 [thread overview]
Message-ID: <486B5814.6000708@trash.net> (raw)
In-Reply-To: <1214930900.9800.32.camel@enterprise.ims-firmen.de>
Thomas Jacob wrote:
> Hello list,
>
> Here's a patch to speed up iptcc_find_chain_by_offset
> (O(n)->O(log(n)) by creating a lookup table while
> initially translating the kernel blob.
>
> In my test case a second iptables-restore with a file containing
> ~50k chains with 120k~ rules takes 11s instead of 1m30s (on a VM).
> iptables -vnL SOMECHAIN takes 0.5s instead of 1m12s.
That sounds great.
> Comments and suggestions would be very welcome, as would
> be inclusion into the mainline distribution ;-)
Please resend the patch inline (or using Content-Disposition: inline;
instead of attachment) so people can view it in their mail clients.
prev parent reply other threads:[~2008-07-02 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 16:48 Further speedup of iptables when modifying an existing ruleset Thomas Jacob
2008-07-02 10:27 ` Patrick McHardy [this message]
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=486B5814.6000708@trash.net \
--to=kaber@trash.net \
--cc=jacob@internet24.de \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox