From: Bart De Schuymer <bdschuym@pandora.be>
To: Michael Bellion <mbellion@hipac.org>
Cc: netfilter-devel@lists.netfilter.org,
netfilter@lists.netfilter.org, Amin Azez <azez@ufomechanic.net>
Subject: Re: [ANNOUNCE] Release of nf-HiPAC 0.9.0
Date: Wed, 09 Nov 2005 22:35:52 +0000 [thread overview]
Message-ID: <1131575752.3423.33.camel@localhost.localdomain> (raw)
In-Reply-To: <200510021430.21697.mbellion@hipac.org>
Op zo, 02-10-2005 te 14:30 +0200, schreef Michael Bellion:
> > Also, is it not possible to make a B+ tree with the standard iptables? I
> > don't see why it shouldn't be possible. The jump to a new chain can be
> > seen as going deeper into the B+ tree. So it should be possible to
> > construct an iptables table structure that looks very similar to the B+
> > tree of nf-hipac, for some given rule set. I guess this will be somewhat
> > slower than nf-hipac, but I'd like to see the performance difference...
>
> Sorry, but you seem to confuse some things.
> nf-HiPAC is not based on B+trees or any other kind of B-trees.
So the algorithm of nf-hipac was changed in view of the one you were
using in 2003? I remembered from your talk then that you used B+trees
and this is confirmed by the slides you've finally put online.
cheers,
Bart
next prev parent reply other threads:[~2005-11-09 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 2:41 [ANNOUNCE] Release of nf-HiPAC 0.9.0 Michael Bellion
2005-09-28 14:05 ` Amin Azez
2005-09-28 19:46 ` Henrik Nordstrom
2005-10-02 11:20 ` Bart De Schuymer
2005-10-02 12:30 ` Michael Bellion
2005-11-09 22:35 ` Bart De Schuymer [this message]
2005-11-10 1:07 ` Michael Bellion
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=1131575752.3423.33.camel@localhost.localdomain \
--to=bdschuym@pandora.be \
--cc=azez@ufomechanic.net \
--cc=mbellion@hipac.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox