[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6a2187b0904101807x77578e0dhd0093d233839ef67@mail.gmail.com>
Date: Sat, 11 Apr 2009 09:07:02 +0800
From: Jeff Chua <jeff.chua.linux@...il.com>
To: Stephen Hemminger <shemminger@...tta.com>
Cc: Eric Dumazet <dada1@...mosbay.com>,
Jan Engelhardt <jengelh@...ozas.de>,
Patrick McHardy <kaber@...sh.net>,
"David S. Miller" <davem@...emloft.net>,
Roman Mindalev <r000n@...0n.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: iptables very slow after commit784544739a25c30637397ace5489eeb6e15d7d49
On Sat, Apr 11, 2009 at 12:52 AM, Stephen Hemminger
<shemminger@...tta.com> wrote:
> The performance benefit during operation is more important. The load
> time is fixable. The problem is probably generic to any set of rules,
> but could you post some info about your configuration (like the rule
> set), and the system configuration (# of cpu's, config etc).
I've about 150 different IPs like ...
iptables -A block -s 155.161.173.128/26 -j ACCEPT
iptables -A block -s 155.161.194.128/26 -j ACCEPT
So, to make it easy for testing, you can do a loop like this ...
for((i = 1; i < 100; i++))
do
iptables -A block -s 10.0.0.$i -j ACCEPT
done
I'm running ThinkPad X61. Dual core T9300, 2.5GHz, 4GB RAM, 256GB SSD.
No load as I was not running anything else, and X not running.
Thanks,
Jeff.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists