From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Thomas Mader <thezema@gmail.com>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: Throughput test for kernelspace module vs. userspace daemon with strange results
Date: Fri, 11 Apr 2008 15:16:53 +0200 [thread overview]
Message-ID: <47FF64C5.9000708@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0804111509140.21182@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Friday 2008-04-11 15:01, Thomas Mader wrote:
>> I thought about explanations for this but I don't come to reasonable
>> explanations for this behaviour. Shouldn't the kernelspace module be faster?
>> Why is it slower?
>
> You are using a raw socket in userspace, which effectively
> bypasses Netfilter.
> To make a meaningful test of it, the PF_RAW code would need
> an NF_HOOK into iptables to make a more accurate comparison I think.
Packets sockets bypass netfilter, raw sockets don't.
I have no explanation for the values you're seeing
though.
next prev parent reply other threads:[~2008-04-11 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 13:01 Throughput test for kernelspace module vs. userspace daemon with strange results Thomas Mader
2008-04-11 13:10 ` Jan Engelhardt
2008-04-11 13:16 ` Patrick McHardy [this message]
2008-04-11 15:01 ` Thomas Mader
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=47FF64C5.9000708@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=thezema@gmail.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