From: King Yung Tong <tong@cs.dal.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Ethloop again and 4 level tree ???
Date: Sat, 08 Jun 2002 18:31:37 +0000 [thread overview]
Message-ID: <marc-lartc-102356115329069@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102355989928437@msgid-missing>
Thank you, Stef
But the result I got using Ethloop is not like that.
I try to start 1:10 at 300k, 1:11 at 100k, since 1:4 parent ceil is 800bps
remind will be 400k.
At time 10s, I put 1:10 at 900k and 1:11 at 900k, and I think the 400kbs
excess will all go to 1:10 and make the flow 1:10 be 700kbs (< 1:4 ceil).
From the ethloop result, 1:10 from 30 go to 50. (equal sharing)
1:11 form 10 go to 30. (eqaul sharing)
Do you think the problem is on HTB script or ethloop script or both????
On Sat, 8 Jun 2002, Stef Coene wrote:
> On Saturday 08 June 2002 20:10, King Yung Tong wrote:
> > Hello again, Thank you for you help last time. I try to create final check
> > for htb, and found some problem. Can you give a quick fix for the problem?
> >
> > 1:1 (ceil 1500kbps)
> > / \
> > (ceil 800kbps) 1:2 1:8 (ceil 700kbps)
> > / \ \
> > 1:4 1:12 1:14
> > / \
> > (prio 0) 1:10 1:11 (prio 1)
> >
> > The tree under 1:2 is almost the same as you example and is working.
> > And I try to build a larger tree (4 levels) and I would like to do
> > following:
> > class 1:14 is completed isolated even no traffic, the BW will not borow.
> > class 1:12 is empty all the time.
> > class 1:10 is prio 0 and class 1:11 is prio 1
> >
> > 1. My understanding is 1:8 and 1:2 are isolated because of ceil and will
> > not borrow?
> > 2. Since 1:12 is always emppty, it can borrow the excess to tree 1:4 and
> > 1:10 will get all the BW.
> >
> > But in my case, the prio parameter seems to be not very ok. It will give
> > BW to both 1:10 and 1:11.
> HTB will try to give each class it's rate as a minimum :
> ./tc class add dev lo parent 1:2 classid 1:10 htb rate 300kbps ceil 800kbps
> prio 0
> ./tc class add dev lo parent 1:2 classid 1:11 htb rate 100kbps ceil 800kbps
> prio 1
>
> So class 1:10 gets 300kbps and class 1:11 gets 100kbps. The other 400kbps
> will go to class 1:10 beacause his prio is lower. So prio is for traffic
> that's left after each class gets his rate.
>
> I hope I'm right, Devik ? :)
>
> 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/
>
_______________________________________________
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-06-08 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 18:10 [LARTC] Ethloop again and 4 level tree ??? King Yung Tong
2002-06-08 18:18 ` Stef Coene
2002-06-08 18:31 ` King Yung Tong [this message]
2002-06-08 23:00 ` Martin Devera
2002-06-09 19:24 ` King Yung Tong
2002-06-10 18:01 ` King Yung Tong
2002-06-10 21:21 ` King Yung Tong
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-102356115329069@msgid-missing \
--to=tong@cs.dal.ca \
--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.