From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB - problem with one thread
Date: Wed, 28 Aug 2002 17:45:53 +0000 [thread overview]
Message-ID: <marc-lartc-103055679503867@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103054061315522@msgid-missing>
On Wednesday 28 August 2002 15:15, Ciprian Nica wrote:
> Hello,
>
> Besides a very good functionality, I have a small, yet stressing, problem.
>
> Let's say I have a bandwidth of N bits.
>
> I have X clients, everyone with his fixed bandwidth.
>
> I create htb qdsics for each client. Each leaf has sfq queueing
> discipline.
>
> A sample config would be like this :
>
> tc class add dev eth0 parent 1:2 classid 1:346 htb rate 32Kbit ceil 32Kbit
> burst 4k cburst 2k prio 4
> tc qdisc add dev eth0 parent 1:346 handle 346 sfq perturb 10
>
> AND
>
> tc class add dev eth0 parent 1:2 classid 1:161 htb rate 256Kbit ceil
> 256Kbit burst 32k cburst 2k prio 4
> tc qdisc add dev eth0 parent 1:161 handle 161 sfq perturb 10
>
>
> The filters are like :
> tc filter add dev eth0 parent 1:0 protocol ip prio 100 u32 match ip dst
> 1.2.3.128/25 classid 1:346 tc filter add dev eth0 parent 1:0 protocol ip
> prio 100 u32 match ip dst 1.2.3.4/30 classid 1:161
>
> The problem is that clients can have their bandwidths at maximum only if
> they use a download accelerating software like DAP with multiple
> symultanous threads. Using only one thread, a single download can reach
> about 60% of the allocated bandwidth.
>
> I have tested a download without any limits and it was working well, so
> there's no problem with the remote site.
>
> I have searched thorugh messages posted on this mailing list but I didn't
> find a similar problem.
>
>
> Maybe I need to set quantum manually. I have tested with r2q default value
> (10) and also with 2 (raising quantum).
>
> Another question would be: if quantum is bigger, the client can exceed his
> limit by that value ? Is that possible all the time or at bursty intervals
> ?
Quantum is used if 2 or more classes with the same parent are fighting for
bandwidth. First, they are allowed to get the rate you gave them. For the
remaining bandwidth, quantum is used. Each class may send quantum bytes.
You have to make sure quantum > MTU (typical 1500 bytes for ethernet).
What if you use no sfq qdiscs?
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.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:[~2002-08-28 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 13:15 [LARTC] HTB - problem with one thread Ciprian Nica
2002-08-28 17:45 ` Stef Coene [this message]
2002-08-29 8:19 ` Ciprian Nica
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-103055679503867@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.