From: jamal <hadi@cyberus.ca>
To: Emmanuel Fleury <fleury@cs.aau.dk>
Cc: Michael Bellion <mbellion@hipac.org>,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [ANNOUNCE] Release of nf-HiPAC 0.9.0
Date: Mon, 26 Sep 2005 08:40:49 -0400 [thread overview]
Message-ID: <1127738450.6215.331.camel@localhost.localdomain> (raw)
In-Reply-To: <4337E601.1070208@cs.aau.dk>
On Mon, 2005-26-09 at 14:13 +0200, Emmanuel Fleury wrote:
> That is right, the add/remove/modifying policies was still an issue when
> we stopped working on this. But, I think we can solve this problem by
> working on an incremental compiler. I have to admit that this require a
> proof of concept. This issue is quite critical on our method.
>
I think if you solve the lookup issue (which you seem to have) and this
you will be in good shape.
> > Several comments:
> > - Am i mistaken that your source of data is from somewhere in the
> > backbone? Would it be fair to say that something in the edge would be
> > more appropriate?
>
> The source of the data has been recorded from a backbone but all the
> clients in the experimental setting are replaying part of it and sending
> it to the gigabit switch.
>
Ok, makes sense.
> > - Is tcpreplay the right tool? What does it give you that you cant use
> > a better blaster like pktgen?
>
> The idea was to replay a realistic traffic. So we used a slightly
> modified version of the tcpreplay (I don't remember what modifications
> have been done, my co-author did it). I should definitely take a look at
> pktgen.
>
Both are useful tests. Benchmarking typically doesnt factor in realistic
- the rule of thumb being if you can win a benchmark you can do better.
The exception is when you make complex changes to win a benchmark; there
has to be a balance.
> > If you are going to run these tests in stateless firewalling as you
> > did, please consider using tc filter as well.
>
> The spirit was to test a totally new idea, the plan was not really to
> get integrated (yet) into any tool, so we did it like this. We might
> have been wrong.
I think the methodology was fine enough for what you were doing then;
academic time constraints apply and you can be forgiven for that ;->
Now that you have gone beyond academia and have some company behind your
work, it is only fair to compare against tc filter because it is in the
kernel and being used by some people.
I am willing to help consult for the tc filter side if you need help.
cheers,
jamal
next prev parent reply other threads:[~2005-09-26 12:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200509260445.46740.mbellion@hipac.org>
2005-09-26 11:18 ` [ANNOUNCE] Release of nf-HiPAC 0.9.0 jamal
2005-09-26 11:24 ` Emmanuel Fleury
[not found] ` <4337DA7C.2000804@cs.aau.dk>
2005-09-26 11:58 ` jamal
2005-09-26 12:13 ` Emmanuel Fleury
2005-09-26 12:40 ` jamal [this message]
2005-09-26 14:38 ` Michael Bellion
[not found] ` <200509261638.12731.mbellion@hipac.org>
2005-09-26 15:05 ` Emmanuel Fleury
[not found] ` <43380E4A.1060604@cs.aau.dk>
2005-09-26 16:03 ` Michael Bellion
[not found] ` <200509261803.28150.mbellion@hipac.org>
2005-09-26 16:31 ` Emmanuel Fleury
2005-10-06 15:09 ` Bill Davidsen
[not found] ` <1127733492.6215.274.camel@localhost.localdomain>
2005-09-26 13:16 ` Michael Bellion
[not found] ` <200509261516.16565.mbellion@hipac.org>
2005-09-26 13:31 ` jamal
2005-09-30 12:33 ` Harald Welte
[not found] ` <20050930123334.GW4168@sunbeam.de.gnumonks.org>
2005-10-01 15:38 ` Michael Bellion
2005-09-26 2:45 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=1127738450.6215.331.camel@localhost.localdomain \
--to=hadi@cyberus.ca \
--cc=fleury@cs.aau.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=mbellion@hipac.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).