All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton <anton.vazir@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: iptables performance and alternatives
Date: Thu, 15 May 2008 16:29:22 +0500	[thread overview]
Message-ID: <200805151629.22785.anton.vazir@gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0805151318020.16151@fbirervta.pbzchgretzou.qr>


On Thursday 15 May 2008 16:18, Jan Engelhardt wrote:
> On Thursday 2008-05-15 12:57, Anton wrote:
> >Definitelly what my test shows - while rule-inserts - if
> > you try to insert 10000 rules - after a several
> > hundreds - it will be inserting like a 1 rule in 1
> > second and slowness will progress :)
>
> Your insertion slowness is probably due to incorrect use
> of iptables.

Possible too. 

But aside of use of IPMARK from xtables, if I have to match 
80  (prio traffic)  22(realtime) port for every customer IP 
and customer's ip too (bulk traffic) for another mark set 
and all with different htb queues - IPMARK will not help 
and in case of, say, 1000 matching IP's, it comes to 4 
queues per , with 3 to use with lending/borrowing (main, 
80, and 22) and 3000 queuses in total, plus POSTROUTING 
mangle rule per park (3000 rules) + 3000 return rules 
(6000) rules and so on. If this PC also do NAT for 
matches - it will come with extra 1000 rules (or single 
IPSET :)

If there is a better approach to this in relation to 
IPTABLES - this would be just great...

  reply	other threads:[~2008-05-15 11:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15  9:21 iptables performance and alternatives Anton
2008-05-15  9:26 ` Jan Engelhardt
2008-05-15 10:35   ` Anton
2008-05-15 10:43     ` Jan Engelhardt
2008-05-15 10:57       ` Anton
2008-05-15 11:18         ` Jan Engelhardt
2008-05-15 11:29           ` Anton [this message]
2008-05-15 12:01             ` Jan Engelhardt
2008-05-15 12:46               ` Anton VG
2008-05-15 13:19           ` Thomas Jacob
2008-05-18 21:15             ` Jesper Dangaard Brouer
2008-05-19  7:51               ` Thomas Jacob
2008-05-19 10:00                 ` Jesper Dangaard Brouer
2008-05-15 12:32         ` Henrik Nordstrom
2008-05-15 12:34           ` Anton VG
2008-05-15  9:34 ` Eric Leblond
2008-05-15  9:58   ` Jan Engelhardt
2008-05-15 11:18     ` Krzysztof Oledzki
2008-05-15 11:58       ` Jan Engelhardt
2008-05-15 11:04   ` Anton
2008-05-15 11:20     ` Jan Engelhardt
2008-05-15 12:28   ` Henrik Nordstrom
2008-05-20  7:42     ` KOVACS Krisztian
2008-05-20 23:53       ` Henrik Nordstrom
2008-05-15 13:46 ` Patrick McHardy

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=200805151629.22785.anton.vazir@gmail.com \
    --to=anton.vazir@gmail.com \
    --cc=jengelh@medozas.de \
    --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 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.