From: Adi Nugroho <Adi@iNterNUX.co.id>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Latency in SFQ
Date: Tue, 18 Dec 2001 10:27:51 +0000 [thread overview]
Message-ID: <marc-lartc-100867094901626@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100865895013266@msgid-missing>
On Tuesday 18 December 2001 16:03, bert hubert wrote:
>
> I think cbq.init is misconfiguring things.
>
Dear Sir,
As your suggestion, I have made all rule by hand.
Bellow are my script, one for cbq (tbf+sfq), and one for htb (+sfq)
But the latency was still so high (sometimes more than 20.000 ms if
overloaded)
From statistic, the overlimit packet is high, but there is no dropped packet
Thank you for your help.
Regards,
Adi Nugroho
========Script for cbq (tbf+sfq)
========dev=eth1
DEVBWDT\x10Mbit
DEVWGHT=1Mbit
tc qdisc del dev eth1 root
tc qdisc add dev $dev root handle 1:0 cbq\
bandwidth $DEVBWDT avpkt 1000 cell 8
tc class add dev $dev parent 1:0 classid 1:1 cbq \
bandwidth $DEVBWDT rate $DEVBWDT weight $DEVWGHT \
prio 8 allot 1514 cell 8 maxburst 20 avpkt 1000
#parent class
tc class add dev eth1 parent 1:1 classid 1:64 cbq \
bandwidth 10Mbit rate 64Kbit weight 6.4Kbit prio 8\
allot 1514 cell 8 maxburst 20 avpkt 1000 bounded
tc qdisc add dev eth1 parent 1:64 tbf \
rate 64Kbit buffer 3000 limit 3000
#Child class #1
tc class add dev eth1 parent 1:64 classid 1:164 cbq \
bandwidth 10Mbit rate 16Kbit weight 1.6Kbit prio 5 \
allot 1514 cell 8 maxburst 20 avpkt 1000
tc qdisc add dev eth1 parent 1:164 sfq \
perturb 5 quantum 4500
tc filter add dev eth1 parent 1:0 protocol ip \
prio 100 u32 match ip dst 10.0.0.222 flowid 1:164
#Child class #2
tc class add dev eth1 parent 1:64 classid 1:264 cbq \
bandwidth 10Mbit rate 16Kbit weight 1.6Kbit prio 5 \
allot 1514 cell 8 maxburst 20 avpkt 1000
tc qdisc add dev eth1 parent 1:264 sfq \
perturb 5 quantum 4500
tc filter add dev eth1 parent 1:0 protocol ip \
prio 100 u32 match ip dst 10.0.0.73 flowid 1:264
#Child class #3
tc class add dev eth1 parent 1:64 classid 1:364 cbq \
bandwidth 10Mbit rate 16Kbit weight 1.6Kbit prio 5 \
allot 1514 cell 8 maxburst 20 avpkt 1000
tc qdisc add dev eth1 parent 1:364 sfq \
perturb 5 quantum 4500
tc filter add dev eth1 parent 1:0 protocol ip \
prio 100 u32 match ip dst 10.0.0.30 flowid 1:364
===========Script for htb (+sfq)
===========tc qdisc add dev eth1 root handle 1: htb
tc class add dev eth1 parent 1: classid 1:1 htb rate 64Kbit burst 15k
tc class add dev eth1 parent 1:1 classid 1:10 htb rate 16Kbit ceil 64Kbit
burst 15k
tc class add dev eth1 parent 1:1 classid 1:20 htb rate 16Kbit ceil 64Kbit
burst 15k
tc class add dev eth1 parent 1:1 classid 1:30 htb rate 16Kbit ceil 64Kbit
burst 15k
tc qdisc add dev eth1 parent 1:10 handle 10: sfq perturb 10
tc qdisc add dev eth1 parent 1:20 handle 20: sfq perturb 10
tc qdisc add dev eth1 parent 1:30 handle 30: sfq perturb 10
u32="tc filter add dev eth1 protocol ip parent 1:0 prio 1 u32"
$u32 match ip dst 10.0.0.222 flowid 1:10
$u32 match ip dst 10.0.0.73 flowid 1:20
$u32 match ip dst 10.0.0.30 flowid 1:30
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-18 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 7:07 [LARTC] Latency in SFQ Adi Nugroho
2001-12-18 8:03 ` bert hubert
2001-12-18 8:45 ` Stef Coene
2001-12-18 10:27 ` Adi Nugroho [this message]
2001-12-18 10:34 ` bert hubert
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=marc-lartc-100867094901626@msgid-missing \
--to=adi@internux.co.id \
--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.