From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ATTN Andreas Klauer: ASCII art + comments, please?
Date: Mon, 06 Mar 2006 01:05:27 +0000 [thread overview]
Message-ID: <440B8AD7.5D569E20@iswest.com> (raw)
In-Reply-To: <440B672D.D9EE1D8@iswest.com>
Andreas Klauer wrote:
>
> On Sun, Mar 05, 2006 at 02:33:17PM -0800, gypsy wrote:
> > Since I understand your ASCII art and comments, I would very much
> > appreciate it if you would draw what you see and criticize the
> > following. Hopefully I'll better understand after that!
>
> Uh, right. Don't take anything I say for granted, though.
Understood.
> > tc qdisc add dev imq0 root handle 1: htb default 20
> >
> > tc class add dev imq0 parent 1: classid 1:2 htb rate 4522kbit ceil \
> > 4760kbit burst 16k cburst 16k quantum 1500
> >
> > tc class add dev imq0 parent 1:2 classid 1:1 htb rate 4522kbit ceil \
> > 4760kbit burst 16k cburst 16k
> >
> > tc class add dev imq0 parent 1:1 classid 1:10 htb rate 2487kbit \
> > ceil 4760kbit burst 16k cburst 16k quantum 1500 prio 1
> >
> > tc class add dev imq0 parent 1:1 classid 1:20 htb rate 2034kbit \
> > ceil 4341kbit burst 10k cburst 16k quantum 1500 prio 4
>
> First, here is what I see:
>
> 1: HTB root qdisc (default 20)
> |
> \--- 1:2 HTB root class (4522kbit/4760kbit)
> |
> \--- 1:1 HTB class (4522kbit/4760kbit)
> |
> \--- 1:10 HTB leaf class (2487kbit/4760kbit)
> \--- 1:20 HTB leaf class (2034kbit/4341kbit)
>
> Now on to the criticising; the root class has a higher ceil than rate.
> However, different rate/ceil makes only sense if there is someone to
> borrow bandwidth from, which is not the case here. The root class
> acquires bandwidth directly from the QDisc, which has unlimited resources,
> as the root class itself is supposed to be the limiting factor. So what
> you have here should practically be no different from a 4760kbit class.
>
> The 1:1 class seems to be useless; it has exactly the same settings
> as it's parent, except for quantum, which is not explicitely set.
> Furthermore, it does not have any siblings. Does not make sense to
> me as such a class will just use exactly the same rate as it's parent.
> Compare the statistics of these two classes below.
>
> > class htb 1:1 parent 1:2 rate 4522Kbit ceil 4760Kbit burst 16Kb cburst
> > 16Kb
> > Sent 7826237 bytes 27128 pkts (dropped 0, overlimits 0)
> > rate 1728bit 4pps
> > lended: 1954 borrowed: 0 giants: 0
> > tokens: 39532 ctokens: 37555
> >
> > class htb 1:2 root rate 4522Kbit ceil 4760Kbit burst 16Kb cburst 16Kb
> > Sent 7826237 bytes 27128 pkts (dropped 0, overlimits 0)
> > rate 1728bit 4pps
> > lended: 0 borrowed: 0 giants: 0
> > tokens: 39532 ctokens: 37555
>
> As for the leaf classes, their rates are fine (add up to the parent
> class rate), except that the parent actually can use 4760kbit rate
> rather than 4522kbit. Their priorities are questionable; using 1 and 4
> here should not be any different from 1 and 2 or 3 and 6 or 0 and 1.
The four is a "leftover", but I want it clear that 1:10 has priority
over 1:20.
> It's one high- and one low-priority class either way. I would probably
> set a priority just for the low priority class, so that it becomes
> more obvious what is intended by this setting here.
>
> That what you wanted?
>
> Regards
> Andreas Klauer
Thank you. Yes, that is exactly what I wanted. It was also every bit
as understandable as I expected, so THANK YOU again.
I thrashed with this because when I set it up with only a 1:1 (where 1:2
is now), NOTHING ever was recorded in the root and no borrowing would
occur. The more I thrashed, the more confused I became. With this, I
think I can fix it.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-03-06 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 22:33 [LARTC] ATTN Andreas Klauer: ASCII art + comments, please? gypsy
2006-03-06 0:20 ` Andreas Klauer
2006-03-06 1:05 ` gypsy [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=440B8AD7.5D569E20@iswest.com \
--to=gypsy@iswest.com \
--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.