All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Fleury <fleury@cs.auc.dk>
To: nf@hipac.org, netfilter-devel@lists.netfilter.org
Subject: Re: [NF-HIPAC] Performance test results available
Date: Thu, 26 Sep 2002 09:48:13 +0200	[thread overview]
Message-ID: <3D92BBBD.1050609@cs.auc.dk> (raw)
In-Reply-To: 200209260003.10724.nf@hipac.org

Hi,

First, your results are really impressive in comparison to iptables...

I was wandering two things:

1) How does behave the CPU load during your test ?

As you are using very powerful machines (which is not often the case in
reality for firewalls and router), I was really wandering how the CPU
power can affect your method.

2) How much space was used to store each of the rulessets ?

Your representation seems to be compact, but I was wandering how ?
Maybe a comparison with the size of the iptables rulessets could
be relevant.

Regards
-- 
Emmanuel

When all else fails, read the instructions.
   -- Allen's Axiom

  reply	other threads:[~2002-09-26  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 22:03 [NF-HIPAC] Performance test results available nf
2002-09-26  7:48 ` Emmanuel Fleury [this message]
2002-09-26 19:17   ` mbellion
2002-10-01  9:08     ` Roberto Nibali
  -- strict thread matches above, loose matches on Subject: below --
2002-10-24 23:26 netfilter

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=3D92BBBD.1050609@cs.auc.dk \
    --to=fleury@cs.auc.dk \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=nf@hipac.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.