From: Thomas Jacob <jacob@internet24.de>
To: Thomas Jacob <jacob@internet24.de>
Cc: Jesper Dangaard Brouer <jdb@comx.dk>,
netfilter-devel@vger.kernel.org,
Patrick McHardy <kaber@trash.net>
Subject: Re: Patches solving the same issue!?
Date: Thu, 3 Jul 2008 00:02:06 +0200 [thread overview]
Message-ID: <20080702220206.GA13845@internet24.de> (raw)
In-Reply-To: <20080702214736.GA13134@internet24.de>
[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]
As addendum, your code runs just as fast, maybe
even a tad faster as mine, and obviously uses
less memory. Oh well...
On Wed, Jul 02, 2008 at 11:47:36PM +0200, Thomas Jacob wrote:
> Oops, sorry about that, I did notice your initial
> set of speed up patches (that's why I was enthusiastically playing
> around with large rule sets and became aware of the issue
> in the first place), but evidently I didn't follow the
> related thread very closely.
>
> I am not familiar enough with the iptables code to decide
> whether or not chains are always sorted by name in the kernel,
> and thus will be sorted if you read them back, but if that's
> the case, of course your method is better, as long as that's
> always the case...
>
> To be honest, I didn't really understand the chain_index code ;)
>
>
> On Wed, Jul 02, 2008 at 10:57:31PM +0200, Jesper Dangaard Brouer wrote:
> >
> > I can see from the list that Thomas Jacob <jacob@internet24.de>, and I
> > have just posted patches solving the same issue.
> >
> > I promised Patrick that I would work on this issue, and I did.
> >
> > Its running on our production servers, and I planned to release the
> > patch today as it has proven stable on production. I guess Thomas was
> > just slightly faster than me ;-)
> >
> > It was actually already released in the CPAN module IPTables::libiptc
> > (ver.0.08 released 2008-06-16).
> >
> >
> > We both use binary search, but with two slightly different approaches.
> >
> > - My patch uses the existing data structure, and the existing
> > algorithm for binary searching.
> >
> > - Thomas builds a new data structure and implements a new binary
> > search algorithm.
> >
> > I must give Thomas that this binary search algo (taken from wikipedia)
> > is much more compact than the existing one.
> >
> > Guess I cannot judge what patch is the best, as I'm biased...
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-07-02 22:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 18:00 [PATCH 0/3] Further speedup of iptables when modifying an existing ruleset Thomas Jacob
2008-07-02 18:00 ` [PATCH 1/3] Speed up verdict to chain_head mapping by using binary search Thomas Jacob
2008-07-02 18:00 ` [PATCH 2/3] Spelling Thomas Jacob
2008-07-02 18:00 ` [PATCH 3/3] Coding style Thomas Jacob
2008-07-02 20:57 ` Patches solving the same issue!? Jesper Dangaard Brouer
2008-07-02 21:47 ` Thomas Jacob
2008-07-02 22:02 ` Thomas Jacob [this message]
2008-07-03 10:53 ` Jesper Dangaard Brouer
2008-07-03 11:17 ` Thomas Jacob
2008-07-03 12:42 ` Patrick McHardy
2008-07-03 14:30 ` Thomas Jacob
2008-07-03 14:33 ` Patrick McHardy
2008-07-04 7:09 ` Jesper Dangaard Brouer
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=20080702220206.GA13845@internet24.de \
--to=jacob@internet24.de \
--cc=jdb@comx.dk \
--cc=kaber@trash.net \
--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