From: King Yung Tong <tong@cs.dal.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] EF and BE
Date: Sat, 25 May 2002 15:25:38 +0000 [thread overview]
Message-ID: <marc-lartc-102234038926496@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102233751725064@msgid-missing>
Dear devik,
Thank you, you are right, in my case,
My structure should look like that :
1.0 (1.5M)
/ \
(0.5M)1.1 1.2 (1M)
/ / \
1.10 1.15 1.20
(EF) (AF) (BE)
If I add the following:
1) Give AF drop priority,
2) Allow AF (1.15) and BE (1.20) sharing 1M (both under 1.2 sharing
between 1.2),
3) EF (1.10) is strickly allocate certain BW (0.5M) from 1.1 since it is
different parent form 1.2).
Do you think the above stucuture is similar to the differential service
in RFC?
Patrick
On Sat, 25 May 2002, Martin Devera wrote:
> Hi,
> you are right. If you create multi-root tree the subtrees
> are independent and can't borrow. Also you don't need to
> create 1.1, you can use 1.10 as root (if you don't want to
> have other classes under 1.1 of course).
> devik
>
> On Sat, 25 May 2002, King Yung Tong wrote:
>
> > Dear Stef,
> >
> > Can you take a look of my script:
> > 1. I would like to create root 1 with classid 1:1 and 1:2 and default 1:2.
> > 2. 1:10 is under 1:1 with htb ceil 1Mbit for EF traffic.
> > 3. 1:2 is directly under 1:0 and 1:20 is under 1:2 for default.
> > 4. I would like to complete seperate 1:1 and 1:2, so that they can't
> > borrow to each other.
> >
> >
> > Since 1.10 and 1.20 have different parent, they can't borrow to each
> > other. Do you think I can differentiate the class in this way?
> >
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-05-25 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 14:36 [LARTC] EF and BE King Yung Tong
2002-05-25 14:49 ` Martin Devera
2002-05-25 15:25 ` King Yung Tong [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-102234038926496@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox