From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc option rate limits traffic??
Date: Mon, 20 Oct 2003 18:42:48 +0000 [thread overview]
Message-ID: <marc-lartc-106667716725837@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106666672311591@msgid-missing>
On Monday 20 October 2003 18:04, Szalka Tamas wrote:
> Hi!
>
> I have a tc ruleset for shaping ingress traffic (with imq):
> // root qdisc
> tc qdisc add dev imq0 root handle 1 htb default 13
> tc class add dev imq0 parent 1: classid 1:2 htb rate 384Kbit ceil 2Mbit
> burst 15k
>
> // www traffic
> tc class add dev imq0 parent 1:2 classid 1:11 htb rate 256Kbit ceil
> 2Mbit burst 15k
> tc qdisc add dev imq0 parent 1:11 handle 11 sfq perturb 10
> tc filter add dev imq0 parent 1:0 protocol ip prio 100 u32 match ip
> sport 80 0xffff match ip dst 10.0.8.0/24 classid 1:11
>
> // default class
> tc class add dev imq0 parent 1:2 classid 1:13 htb rate 56Kbit ceil 2Mbit
> burst 15k
> tc qdisc add dev imq0 parent 1:13 handle 13 sfq perturb 10
>
> I can download only with ~40 Kbyte/s (~256Kbit), as if the RATE
> parameter gives a limit for downloading, not a guaranteed bandwidth...
> The tc should give the total 2Mbit bandwidth, while there's no other
> traffic on the link.
> Have you experienced similar?
Try to remove the burst parameter.
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-10-20 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 16:04 [LARTC] tc option rate limits traffic?? Szalka Tamas
2003-10-20 18:42 ` 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-106667716725837@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