From: Patrick McHardy <kaber@trash.net>
To: Jeho Park <jhpark-nf@kernelproject.org>
Cc: mbellion@hipac.org, netfilter-devel@lists.netfilter.org,
kulnet@kulnet.kuleuven.be,
Steven Van Acker <deepstar+NRpGDEuW@singularity.be>
Subject: Re: status of nf-HIPAC integration ?
Date: Wed, 23 Aug 2006 13:29:23 +0200 [thread overview]
Message-ID: <44EC3C13.5030506@trash.net> (raw)
In-Reply-To: <44EC08DE.2080107@kernelproject.org>
Jeho Park wrote:
> todays, i tested thputs with smartbits (nf-hipac vs iptables) in the
> kernel 2.6.17.3
> result URL:
> http://www.kernelproject.org/people/jhpark/fw_thput_test1.htm
>
> the result looks somewhat ugly because thput result is much low.
> but as you refer my result, you can compare thput of the iptables with
> that of the nf-hipac in the kernel 2.6.17.3
That indeed looks ugly (for iptables). How was the ruleset structured?
Could you put it on your page please?
next prev parent reply other threads:[~2006-08-23 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 14:57 status of nf-HIPAC integration ? Steven Van Acker
2006-08-23 7:50 ` Jeho Park
2006-08-23 11:29 ` Patrick McHardy [this message]
2006-08-23 14:03 ` Jeho Park
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=44EC3C13.5030506@trash.net \
--to=kaber@trash.net \
--cc=deepstar+NRpGDEuW@singularity.be \
--cc=jhpark-nf@kernelproject.org \
--cc=kulnet@kulnet.kuleuven.be \
--cc=mbellion@hipac.org \
--cc=netfilter-devel@lists.netfilter.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.