All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Vasilenko <acid@dg.net.ua>
To: lartc@vger.kernel.org
Subject: [LARTC] htb2 -> htb3 problems
Date: Tue, 06 Apr 2004 06:16:35 +0000	[thread overview]
Message-ID: <20040406061635.GA3453@dg.net.ua> (raw)

Hello!

I need to switch from htb2 to htb3, because of speed issues (for me,
htb2 is unable to handle more then 100mbit duplex with ~550 classes),
kernel profiling shows htb_dequeue_prio at 1st place with 3x isolation.

So, I've moved from 2.4.19 to 2.4.25 kernel (hi-pac for classification/marking
and htb3 for queueing), and traffic rate drop from 100 to 20mbit.

What can be wrong? The only change I see is htb2 -> htb3


Here is my qdiscs/classes/filters example

qdisc htb 1: dev eth0 r2q 10 default 2500 direct_packets_stat 4604 ver 3.13
qdisc sfq 100: dev eth0 quantum 1514b limit 128p flows 128/1024 perturb 5sec
qdisc sfq 3300: dev eth0 quantum 1514b limit 128p flows 128/1024 perturb 5sec
qdisc sfq 3301: dev eth0 quantum 1514b limit 128p flows 128/1024 perturb 5sec
qdisc sfq 3302: dev eth0 quantum 1514b limit 128p flows 128/1024 perturb 5sec
qdisc sfq 3304: dev eth0 quantum 1514b limit 128p flows 128/1024 perturb 5sec
qdisc sfq 3305: dev eth0 quantum 1514b limit 128p flows 128/1024 perturb 5sec
qdisc sfq 3306: dev eth0 quantum 1514b limit 128p flows 128/1024 perturb 5sec
qdisc sfq 3308: dev eth0 quantum 1514b limit 128p flows 128/1024 perturb 5sec
[skip]


class htb 1:1 root rate 200Mbit ceil 200Mbit burst 263690b/8 mpu 0b cburst 263690b/8 mpu 0b level 7
class htb 1:2 root rate 200Mbit ceil 200Mbit burst 263690b/8 mpu 0b cburst 263690b/8 mpu 0b level 7
class htb 1:3300 parent 1:1 leaf 3300: prio 0 quantum 13107 rate 1Mbit ceil 1126Kbit burst 1023b/8 mpu 0b cburst 0b/8 mpu 0b level 0
class htb 1:3301 parent 1:1 leaf 3301: prio 0 quantum 10240 rate 800Kbit ceil 1Mbit burst 1023b/8 mpu 0b cburst 0b/8 mpu 0b level 0
class htb 1:3302 parent 1:1 leaf 3302: prio 0 quantum 13107 rate 1Mbit ceil 1200Kbit burst 2Kb/8 mpu 0b cburst 0b/8 mpu 0b level 0
class htb 1:3304 parent 1:1 leaf 3304: prio 0 quantum 4915 rate 384Kbit ceil 384Kbit burst 2Kb/8 mpu 0b cburst 0b/8 mpu 0b level 0
[skip]


filter parent 1: protocol ip pref 50 fw
filter parent 1: protocol ip pref 50 fw handle 0x14b4 classid 1:5300
filter parent 1: protocol ip pref 50 fw handle 0x14b5 classid 1:5301
filter parent 1: protocol ip pref 50 fw handle 0x14b6 classid 1:5302
filter parent 1: protocol ip pref 50 fw handle 0x14b8 classid 1:5304
filter parent 1: protocol ip pref 50 fw handle 0x14b9 classid 1:5305
filter parent 1: protocol ip pref 50 fw handle 0x14ba classid 1:5306
[skip]

-- 
Michael Vasilenko
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-04-06  6:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06  6:16 Michael Vasilenko [this message]
2004-04-06  6:33 ` [LARTC] htb2 -> htb3 problems devik
2004-04-06  6:46 ` Michael Vasilenko
2004-04-06  7:15 ` devik
2004-04-06 11:53 ` Michael Vasilenko
2004-04-06 11:55 ` Michael Vasilenko
2004-04-06 12:02 ` devik
2004-04-06 12:56 ` Michael Vasilenko
2004-04-06 13:06 ` devik
2004-04-06 13:27 ` Michael Vasilenko
2004-04-07  5:51 ` Martin Devera
2004-04-07 10:13 ` Michael Vasilenko

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=20040406061635.GA3453@dg.net.ua \
    --to=acid@dg.net.ua \
    --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.