All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandru Dragoi <alex@zoomnet.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] big problem with HTB/CBQ and CPU for more than 1.700
Date: Mon, 28 May 2007 13:53:55 +0000	[thread overview]
Message-ID: <465ADEF3.8040507@zoomnet.ro> (raw)
In-Reply-To: <20070526135435.C96F540DB@outpost.ds9a.nl>

VladSun wrote:
> Alexandru Dragoi написа:
>> u32 hash filters is the key, as somebody pointed. You can also tune your
>> iptables setup, like this
>>
>> #192.168.1.0/24
>> iptables -t mangle -N 192-168-1-0-24
>> iptables -t mangle -A FORWARD -s 192.168.1.0/24 -j 192-168-1-0-24
>> iptables -t mangle -N 192-168-1-0-25
>> iptables -t mangle -N 192-168-1-128-25
>> iptables -t mangle -A 192-168-1-0-24 -s 192.168.1.0/25 -j 192-168-1-0-25
>> iptables -t mangle -A 192-168-1-0-24 -s 192.168.128.0/25 -j
>> 192-168-1-128-25
>> .
>> .
>> and so on, until (ip 192.168.1.11, which is called in chain created for
>> 192.168.1.10/31)
>>
>> iptables -t mangle -A 192-168-1-10-31 -s 192.168.1.10 -j CLASSIFY
>> --set-class 1:10
>> iptables -t mangle -A 192-168-1-10-31 -s 192.168.1.11 -j CLASSIFY
>> --set-class 1:11
>>
>> .. I guess you got the ideea, it requires some RAM, which i belive is
>> not such a big problem. Similar rules should be made for download.
>>
>>   
> Or you can use my patch - IPCLASSIFY. Then the rules above would be
> substituted by a signle rule per direction:
>
>
> iptables -t mangle -A FORWARD -s 192.168.1.0/24 -j IPCLASSIFY
> --addr=src --and-mask=0xff --or-mask=0x11000
> iptables -t mangle -A FORWARD -d 192.168.1.0/24 -j IPCLASSIFY
> --addr=dst --and-mask=0xff --or-mask=0x12000
>
> This is equal to applying CLASSIFY target to each packet with
> --set-class (srcIP & 0xFF | 0x1100 ) and --set-class (dstIP & 0xFF |
> 0x1200 ).
> It is very similar to IPMARK, but it uses skb->priority field instead
> mark. So no tc filters are needed.
>
Cool, I remember I red about this a little while ago. Now, another thing
to tune would be some htb paches for massive hashing on classid lookup.
I must say I haven't use it so far, I hope I will do it soon.

http://www.mail-archive.com/lartc@mailman.ds9a.nl/msg16279.html
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-05-28 13:53 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
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 [this message]
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=465ADEF3.8040507@zoomnet.ro \
    --to=alex@zoomnet.ro \
    --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 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.