From: Susan Hinrichs <shinrich@thought-mesh.net>
To: casper@meteor.dp.ua
Cc: Martin Millnert <millnert@csbnet.se>,
Oskar Berggren <oskar.berggren@gmail.com>,
netfilter@vger.kernel.org
Subject: Re: Select chain from set?
Date: Tue, 28 Apr 2009 10:39:00 -0500 [thread overview]
Message-ID: <1240933140.12894.366.camel@chichi> (raw)
In-Reply-To: <1240925694.4256.32.camel@casper.meteor.dp.ua>
I also agree that a runtime structure to track traffic attributes and
match them to targets would be great. I created my own match-tree table
generator to achieve a similar effect. It works, but updating large
static structures can be rather time consuming and fragile.
I have a question about the '-g' terminology used by Casper and Oscar.
Is this a new piece of functionality? Or are you talking about the
--goto option?
Susan
> > This all begs the question on how effective some tree structure with -g
> > is implemented, to figure out how much of a performance benefit such a
> > new target would have over a treelike chain structure.
>
> If we compare many linear -g with just one function gettarget(ip) the
> different is many/one. Tree-like -g structure would save most
> comparitions, but is hard to write for every task. Function-like target
> is real fast and fully automatic, the only disadvantage is in fact it
> doesn't exist :)
>
next prev parent reply other threads:[~2009-04-28 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 9:21 Select chain from set? Oskar Berggren
2009-04-28 12:27 ` Martin Millnert
2009-04-28 13:34 ` Покотиленко Костик
2009-04-28 15:39 ` Susan Hinrichs [this message]
2009-04-29 8:11 ` Покотиленко Костик
2009-04-30 15:52 ` Susan Hinrichs
2009-05-07 10:07 ` Покотиленко Костик
2009-05-07 13:44 ` Susan Hinrichs
2009-05-07 14:01 ` Thomas Jacob
2009-05-07 14:31 ` Susan Hinrichs
2009-05-07 14:57 ` Thomas Jacob
2009-05-07 15:48 ` Покотиленко Костик
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=1240933140.12894.366.camel@chichi \
--to=shinrich@thought-mesh.net \
--cc=casper@meteor.dp.ua \
--cc=millnert@csbnet.se \
--cc=netfilter@vger.kernel.org \
--cc=oskar.berggren@gmail.com \
--cc=shinrich@ieee.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