From: Roberto Nibali <ratz@drugphish.ch>
To: jamal <hadi@cyberus.ca>
Cc: niv@us.ibm.com, linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [ANNOUNCE] NF-HIPAC: High Performance Packet Classification
Date: Thu, 26 Sep 2002 22:23:21 +0200 [thread overview]
Message-ID: <3D936CB9.1040706@drugphish.ch> (raw)
In-Reply-To: Pine.GSO.4.30.0209260739030.29224-100000@shell.cyberus.ca
Hello Jamal,
[took out AK und DaveM since I know they both read netdev and this reply
is not really of any relevance to them]
> It would be nice if people would start ccing networking related
> discussions to netdev. I missed the first part of the discussion
> but i take it the NF-HIPAC posted a patch.. BTW, I emailed the authors
Yes, your assumption is correct and sorry for missing the cc once again.
> when i read the paper but never heard back.
> What i wanted the authors was to compare against one of the tc
> classifiers not iptables.
I will contact you privately on this issue since I'm about to conduct
tests this weekend.
> I hacked some code using the traffic control framework around OLS time;
> there are a lot of ideas i havent incorporated yet. Too many hacks, too
> little time ;-> I think this is what i may have showed Roberto on my
> laptop over a drink.
Exactly (even wearing a netfilter T-shirt).
> I probably wouldnt have put this code out if my complaints about
> netfilter werent ignored.
> And you know what happens when you start writting poetry, I ended worrying
> more than just about the performance problems of iptables; for example
> the code i have now makes it easy to extend the path a packet takes using
> simple policies.
Great, I remember some of your postings about the netfilter framework.
> The code i have is based around tc framework. One thing i liked about
> netfilter is the idea of targets being separate modules; so the code i
> have infact makes uses of netfilter targets.
> I plan on revisiting this code at some point, maybe this weekend now that
> i am reminded of it ;->
Excellent, this could make it into my test suites as well.
> Take a look:
> http://www.cyberus.ca/~hadi/patches/action.DESCRIPTION
I did, I simply didn't find the time to do it.
> Agreed, you need a netlink to syslog converter.
> Netlink is king -- all the policies in the above code are netlink
> controlled. All events are also netlink transported. You dont have to send
> every little message you see; netlink allows you to batch and you could
> easily do a nagle like algorithm. Next steps are a distributed version
> of netlink..
Is there a code architecture draft somewhere?
Best regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
next prev parent reply other threads:[~2002-09-26 20:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D924F9D.C2DCF56A@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <20020925.170336.77023245.davem@redhat.com.suse.lists.linux.kernel>
2002-09-26 0:31 ` [ANNOUNCE] NF-HIPAC: High Performance Packet Classification Andi Kleen
2002-09-26 0:29 ` David S. Miller
2002-09-26 0:46 ` Andi Kleen
2002-09-26 0:44 ` David S. Miller
2002-09-26 9:00 ` Roberto Nibali
2002-09-26 9:06 ` David S. Miller
2002-09-26 9:24 ` Roberto Nibali
2002-09-26 9:21 ` David S. Miller
2002-09-26 15:13 ` James Morris
2002-09-26 20:51 ` Roberto Nibali
2002-09-26 10:25 ` Roberto Nibali
2002-09-26 10:20 ` David S. Miller
2002-09-26 10:49 ` Roberto Nibali
2002-09-26 12:03 ` jamal
2002-09-26 20:23 ` Roberto Nibali [this message]
2002-09-27 13:57 ` jamal
2002-09-26 12:04 ` Andi Kleen
2002-09-26 20:49 ` Roberto Nibali
2002-09-30 17:36 ` Bill Davidsen
2002-10-02 17:37 ` Roberto Nibali
2002-09-26 1:17 ` Nivedita Singhvi
2002-09-26 1:15 ` Andi Kleen
2002-09-26 0:06 Nivedita Singhvi
2002-09-26 0:03 ` David S. Miller
2002-09-26 0:50 ` Nivedita Singhvi
2002-09-26 0:40 ` David S. Miller
2002-09-26 1:09 ` Nivedita Singhvi
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=3D936CB9.1040706@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.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;
as well as URLs for NNTP newsgroup(s).