From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TBF tunning
Date: Fri, 07 Nov 2003 18:05:28 +0000 [thread overview]
Message-ID: <marc-lartc-106822842731966@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106822722330358@msgid-missing>
On Friday 07 November 2003 18:34, Maria Joana Urbano wrote:
> Hi all,
>
> I am trying to tune tbf qdisc. My upstream configuration is as follows:
>
> tc qdisc add dev $DEV root handle 1: cbq avpkt 1000 bandwidth 100mbit
> tc class add dev $DEV parent 1:0 classid 1:1 cbq rate ${UP_RATE}kbit \
> allot 1500 prio 5 bounded
> tc qdisc add dev $DEV parent 1:1 handle 10: tbf rate ${UP_RATE}kbit \
> burst $BURST limit $LIMIT mtu $MTU
> tc filter add dev $DEV parent 1:0 protocol ip prio 18 u323 match ip \
> dst 0.0.0.0/0 flowid 1:1
>
> I tried several combinations of BURST (from 10KB until there is no pkt
> drops at tbf) and LIMIT values (corresponding to latencies of 40ms, 70ms
> and 140ms). MTU is set to 1500, the MTU of the link. I tested this
> configuration with several combinations of TCP flows and UDP flows
> (seperately). However, the best value I got for throughput was about 90%
> of UP_RATE.
>
> My question is: is it possible to get better results with tbf, with
> throughput values closer to UP_RATE? And what should be changed in the
> script above to get it better?
You don't need a tbf qdisc if you have a bounded class. The traffic is
already bounded by the cbq class.
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/
prev parent reply other threads:[~2003-11-07 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 17:34 [LARTC] TBF tunning Maria Joana Urbano
2003-11-07 18:05 ` Stef Coene [this message]
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-106822842731966@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 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.