From: Emmanuel Fleury <fleury@cs.aau.dk>
To: Michael Bellion <mbellion@hipac.org>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [ANNOUNCE] Release of nf-HiPAC 0.9.0
Date: Mon, 26 Sep 2005 18:31:45 +0200 [thread overview]
Message-ID: <43382271.90400@cs.aau.dk> (raw)
In-Reply-To: <200509261803.28150.mbellion@hipac.org>
Michael Bellion wrote:
>
> Sorry, but this is far away from the worst case for your scheme. Actually it
> is a quite good case for your compiler, because every rule is fully specified
> (meaning there are no wildcards in any rule) and there are no ranges or masks
> involved.
> Try using a mixed rule set that contains rules that only specify certain
> dimensions and have wildcards on the other dimensions. Try using rules with
> ranges and masks.
> Try using overlapping rules, meaning rules that completely or partly overlap
> other rules in certain dimensions.
> This will make your data structure grow!
I think you misunderstood our experiment. In fact, we were trying to
generate as much possible different singletons on the domain (each of
our rule was the header of a packet which have not been seen before),
because if we can group these rules into intervals, then our scheme is
having some advantages.
We were using IDD (Interval Decision Diagrams) which is a kind of
extended BDD (Binary Decision Diagrams) where you take your decision by
looking at a partition of the possible values of the variable. For
example, looking at the value x in [0,1024] where [0,128] leads to one
node in the decision tree, [129,256] to another and [257,1024] to a last
one. More this partition is fragmented more you increase the size of the
structure. Having a lot of overlap does certainly increase the number of
partitions, but adding singletons is the simplest way to increase the
number of partitions.
Take a look at this paper, maybe you can get some idea for your scheme
(it might be that some hybrid between your ideas and ours can make it):
http://www.cs.aau.dk/~fleury/download/papers/tc04.pdf
> Yes, you are right. The HiPAC project has gone through some tough times over
> the last 2 years. With MARA Systems the HiPAC Project has finally found a
> strong partner that is fully committed to the concept of Open Source
> Software. This allows me to continue the development of HiPAC under the GNU
> GPL license.
I'm always happy to see a firm funding some Open Source project. So, I
can do anything else but wishing you good luck for the future. :)
> Ok, I'll do that :)
Good. :)
Regards
--
Emmanuel Fleury
As usual, goodness hardly puts up a fight.
-- Calvin & Hobbes (Bill Waterson)
next prev parent reply other threads:[~2005-09-26 16:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 2:45 [ANNOUNCE] Release of nf-HiPAC 0.9.0 Michael Bellion
2005-09-26 11:18 ` jamal
2005-09-26 13:16 ` Michael Bellion
2005-09-26 13:31 ` jamal
2005-09-26 11:24 ` Emmanuel Fleury
2005-09-26 11:58 ` jamal
2005-09-26 12:13 ` Emmanuel Fleury
2005-09-26 12:40 ` jamal
2005-09-26 14:38 ` Michael Bellion
2005-09-26 15:05 ` Emmanuel Fleury
2005-09-26 16:03 ` Michael Bellion
2005-09-26 16:31 ` Emmanuel Fleury [this message]
2005-09-30 12:33 ` Harald Welte
2005-10-01 15:38 ` 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=43382271.90400@cs.aau.dk \
--to=fleury@cs.aau.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=mbellion@hipac.org \
--cc=netdev@oss.sgi.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