All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Kucheria <amitk@ittc.ku.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB equivalent for 'bounded' and 'isolated' in CBQ
Date: Fri, 16 Aug 2002 21:09:15 +0000	[thread overview]
Message-ID: <marc-lartc-102953224700762@msgid-missing> (raw)

Hi all,

Sally Floyd's Link sharing paper defines the following:

1. Bounded class: class that is not allowed to borrow from ancestor 
classes, regardless of the limit status of those classes.

2. Isolated class: class that does not allow non-descendant classes to 
borrow its unused bandwidth and that does not borrow bandwidth from 
other classes in turn

How does HTB implement a 'bounded class'? I seem to see no constructs to 
be able to do this.

The 'ceil' parameter allows us to implement a part of the 'isolated'
definition above. By setting it equal to 'rate', the class does not
borrow bandwidth, but what will stop other classes from borrowing its
unused bandwidth?

Regards,
Amit

--
I'm an angel!!! Honest!
The horns are just there to hold the halo up straight.
^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^
                  Amit Kucheria
          EECS Grad. Research Assistant
         University of Kansas @ Lawrence
   (R): +1-785-830-8521 ||| (C): +1-785-760-2871
____________________________________________________

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-08-16 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16 21:09 Amit Kucheria [this message]
2002-08-18 20:01 ` [LARTC] HTB equivalent for 'bounded' and 'isolated' in CBQ Stef Coene
2002-08-21  3:32 ` Amit Kucheria
2002-08-21 17:48 ` Stef Coene
2002-08-29  6:26 ` Radosław Łoboda
2002-08-29 13:08 ` Stef Coene

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-102953224700762@msgid-missing \
    --to=amitk@ittc.ku.edu \
    --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.