From: Amin Azez <azez@ufomechanic.net>
To: John Ye <johny@asimco.com.cn>
Cc: netfilter-devel@vger.kernel.org, YE QY <iceburgue@gmail.com>
Subject: Re: remarkably Increase iptables' speed on SMP system.
Date: Fri, 28 Sep 2007 13:18:41 +0100 [thread overview]
Message-ID: <46FCF121.8010807@ufomechanic.net> (raw)
In-Reply-To: <00de01c80175$7402ef90$ca8510ac@asimco>
* John Ye wrote, On 28/09/07 03:15:
> There is a kernel patch to let softirq network code(iptables included in) concurrently run on every CPUs on SMP system.
> We wrote the kernel patch, a loadable module as well, to totally resolve iptables SMP issue.
> Have discussed with kernel netdev experts. it should be working.
>
> The patch(module) will greatly increase the speed of iptalbes by making full use of every CPUs in SMP system.
>
> It can be viewed and downloaded from blog http://blog.chinaunix.net/u/12848/showart.php?id=389602
> You are welcome to review and test without patching and re-compiling the kerenl.
This looks interesting, and I hope worthwhile.
I wonder if it will likely re-order packets with the same flow?
i.e. packets which take more processing may leave the bridge/router
after a packet of the same flow which arrived later.
Cases where this seems more likely are generally where not every packet
of the same flow requires the same level of processing.
Obvious examples are:
* udp snat, where only the first packet follows the nat table
* layer7 when it stops matching, the very next packet may get through
before the one that was the last to be matched.
* packet count or rate based rules that only sometimes call secondary
chains may be delayed more than the next packet if it doesn't match.
TCP (with SACK) may not be so bothered about this, but some GRE or UDP
protocols may care (get degraded service), it may also foil upstream
flow analysis which makes me realise that the layer7 match (and probably
string match) are open to being deceived by deliberate out-of-order
packets or intermediate fake packets with bad tcp sequence numbers. Hmm
Sam
next prev parent reply other threads:[~2007-09-28 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 2:15 remarkably Increase iptables' speed on SMP system John Ye
2007-09-28 12:18 ` Amin Azez [this message]
2007-09-28 13:29 ` Henrik Nordstrom
2007-09-28 16:01 ` Rennie deGraaf
2007-09-29 9:52 ` John Ye
2007-10-01 7:21 ` john ye
2007-10-01 12:10 ` john ye
2007-10-08 12:04 ` john ye
2007-10-08 16:40 ` Patrick McHardy
2007-10-10 1:48 ` John Ye
2007-09-28 13:52 ` Jan Engelhardt
[not found] <001201c80298$3509ac10$0201a8c0@ibmea4709fd199>
2007-09-29 13:23 ` john ye
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=46FCF121.8010807@ufomechanic.net \
--to=azez@ufomechanic.net \
--cc=iceburgue@gmail.com \
--cc=johny@asimco.com.cn \
--cc=netfilter-devel@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).