Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Marek Kierdelewicz <marek@piasta.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] big problem with HTB/CBQ and CPU for more than 1.700
Date: Sat, 26 May 2007 14:22:10 +0000	[thread overview]
Message-ID: <20070526162210.753a8d69@catlap> (raw)
In-Reply-To: <20070526135435.C96F540DB@outpost.ds9a.nl>

>Hello,

Hi there!
 

>iptables -t mangle -A POSTROUTING --dest x.x.x.x -o eth0 -j CLASSIFY
>--set-class 1:5
>iptables -t mangle -A FORWARD --src x.x.x.x -o eth1 -j CLASSIFY
>--set-class 1:5

3k iptables rules strike me as something suicidaly slow.

Try using tc hashing filters for traffic classification as described
here:
http://lartc.org/howto/lartc.adv-filter.hashing.html

If you use private addresses and NAT then you'll need IFB
(http://linux-net.osdl.org/index.php/IFB) to shape upload per client
with u32 hashing filters.

Hope that helps.

pozdrawiam,
Marek Kierdelewicz
KoBa ISP
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2007-05-26 14:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26  9:54 [LARTC] big problem with HTB/CBQ and CPU for more than 1.700 Pablo Fernandes Yahoo
2007-05-26 14:22 ` Marek Kierdelewicz [this message]
2007-05-26 15:23 ` VladSun
2007-05-26 16:22 ` Acácio Alves dos Santos
2007-05-27 22:46 ` Stoimen Gerenski
2007-05-28  0:27 ` Pablo Fernandes Yahoo
2007-05-28 10:01 ` AW: " Pablo Fernandes Yahoo
2007-05-28 13:15 ` Acácio Alves dos Santos
2007-05-28 13:29 ` Alexandru Dragoi
2007-05-28 13:39 ` VladSun
2007-05-28 13:53 ` Alexandru Dragoi
2007-06-01  2:43 ` Luciano Ruete
2007-06-01 12:00 ` VladSun

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=20070526162210.753a8d69@catlap \
    --to=marek@piasta.pl \
    --cc=lartc@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