From: nf@hipac.org
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] NF-HIPAC: High Performance Packet Classification for Netfilter
Date: Thu, 26 Sep 2002 03:44:26 +0200 [thread overview]
Message-ID: <200209260344.26814.nf@hipac.org> (raw)
In-Reply-To: <20020925.173728.08323077.davem@redhat.com>
> Seriously, just sit tight with your work, and once the stackable
> route stuff is done, you can look into applying your algorithms
> to the new flow cache.
Sorry, we are a bit confused of the formulation "adding the algorithmus to the
new flow cache"
Why to the flow cache? What exaclty is the job of this flow cache?
Does the job go beyond caching recently "lookup results"?
What happens if the flow cache doesn't have a certain lookup result in the
cache yet?
We mean, how is the packet classification solved then?
Is it right, that the code will then use a linear search algorithm and compare
the packet with each rule sequentially until a rule is found that matches all
relevant fields?
Our algorithm does not implement some kind of cache. Our algorithm is actually
a replacement for that linear search algorithm. Our algorithm implements an
advanced approach to the packet classification problem itself.
the nf-hipac team
Michael Bellion, Thomas Heinz
next prev parent reply other threads:[~2002-09-26 1:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 22:41 nf
2002-09-25 22:52 ` David S. Miller
2002-09-26 0:10 ` Rik van Riel
2002-09-26 0:25 ` David S. Miller
2002-09-26 0:38 ` nf
2002-09-26 0:37 ` David S. Miller
2002-09-26 1:44 ` nf [this message]
2002-09-26 3:30 ` David S. Miller
2002-09-26 5:19 ` Rusty Russell
2002-09-26 5:40 ` David S. Miller
2002-09-26 15:27 ` James Morris
2002-09-26 20:52 ` David S. Miller
2002-09-27 3:00 ` Michael Richardson
2002-09-27 14:12 ` jamal
2002-09-28 1:30 ` David S. Miller
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=200209260344.26814.nf@hipac.org \
--to=nf@hipac.org \
--cc=davem@redhat.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®