From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] imprecision in bandwidth measurement
Date: Fri, 05 Dec 2003 18:17:44 +0000 [thread overview]
Message-ID: <marc-lartc-107064833506837@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107064353600414@msgid-missing>
On Friday 05 December 2003 18:23, Tilman Giese (Global View) wrote:
> Stef Coene wrote:
> >Can you post us your tc commands ?
>
> # tc qdisc add dev eth0 root handle 1: cbq bandwidth 10MBit allot 1514
> cell 8 avpkt 1000 mpu 64
> # tc filter add dev eth0 parent 1:0 prio 5 protocol ip u32
>
> # tc class add dev eth0 parent 1:0 classid 1:1 cbq bandwidth 10MBit rate
> 10MBit allot 1514 cell 8 weight 1MBit prio 5 maxburst 20 avpkt 1000 bounded
> # tc class add dev eth0 parent 1:1 classid 1:2 cbq bandwidth 750KBit
> rate 750KBit avpkt 1000 cell 8 prio 5 allot 1514 weight 75KBit maxburst
> 21 bounded
> # tc class add dev eth0 parent 1:2 classid 1:3 cbq bandwidth 750KBit
> rate 50KBit avpkt 1000 cell 8 prio 5 allot 1514 weight 5KBit maxburst 21
>
> # tc filter add dev eth0 parent 1: prio 5 u32 match ip src
> 192.168.0.33/32 flowid 1:3
I don't see any error in your scripts. I did some tests myself and this is
the result :
http://docum.org/stef.coene/qos/tests/cbq/bounded/bounded.html
I had the same result. The bandwidth you get is a bit more then the
configured rate.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-05 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 16:51 [LARTC] imprecision in bandwidth measurement Tilman Giese (Global View)
2003-12-05 17:10 ` Stef Coene
2003-12-05 17:23 ` Tilman Giese (Global View)
2003-12-05 18:17 ` Stef Coene [this message]
2003-12-05 19:44 ` Patrick McHardy
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-107064833506837@msgid-missing \
--to=stef.coene@docum.org \
--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