Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Yacine" <yacine@alyseo.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Consider r2q change, why !?
Date: Sun, 13 Jun 2004 13:24:34 +0000	[thread overview]
Message-ID: <00f301c45149$c4cfed40$1002a8c0@windaube> (raw)

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

Hi,

My system always complain with the warning below :
HTB: quantum of class 10099 is small. Consider r2q change.

I simply do not understand why...

Below my tc commands :
/sbin/tc qdisc del dev eth0 root
/sbin/tc qdisc add dev eth0 root handle 1 htb default 99

/sbin/tc class add dev eth0 parent 1: classid 1:2 htb rate 128Kbit

/sbin/tc class add dev eth0 parent 1:2 classid 1:10 htb rate 80Kbit ceil
128Kbit prio 0
/sbin/tc qdisc add dev eth0 parent 1:10 handle 10 sfq perturb 10
/sbin/tc filter add dev eth0 parent 1:0 protocol ip prio 100 u32 match ip
dst ***.***.***.*** classid 1:10

/sbin/tc class add dev eth0 parent 1:2 classid 1:99 htb rate 48Kbit ceil
48Kbit prio 7
/sbin/tc qdisc add dev eth0 parent 1:99 handle 99 sfq perturb 10

My default class quantum (99) is correct I guess :  quantum is >
1500 (my MTU).
If I change the rate of my default class to something >= 79 Kbit then it
work without any warning !?!?

I am just looking for an explanation as I'm lost here...

FYI :
#  tc -V
tc utility, iproute2-ss001007
#  uname -r
2.4.26
#  ip link sh eth0
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc htb qlen 1000
    link/ether 00:40:63:c9:b3:32 brd ff:ff:ff:ff:ff:ff

Thanks,
Yacine.

[-- Attachment #2: Type: text/html, Size: 1776 bytes --]

             reply	other threads:[~2004-06-13 13:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-13 13:24 Yacine [this message]
2004-06-13 16:01 ` [LARTC] Consider r2q change, why !? Clifford Payne

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='00f301c45149$c4cfed40$1002a8c0@windaube' \
    --to=yacine@alyseo.com \
    --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