All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Golubev <dmitry@mikrotik.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB theory?
Date: Wed, 16 Jun 2004 15:31:44 +0000	[thread overview]
Message-ID: <200406161831.44991.dmitry@mikrotik.com> (raw)
In-Reply-To: <200406121446.08416.dmitry@mikrotik.com>

Thanks very much, Devik and Andy, I had seminar today and I think it has some 
success, and (for now?) I do not feel like having unanswered questions.

Dmitry

On Sunday 13 June 2004 21:41, Martin Devera <devik@cdi.cz> wrote:
> > 1. In order of priority, we satisfy all leaf classes' rates (while the
> > class is “green”)
> > 2. When the leaf classes' rate is reached (all the leaf classes are
> > “yellow”), borrow the unused speed from parent classes if they have
> > something to give (if they are not “red”). In this case, each leaf class
> > is equal to others until their ceil is met or until they will have no
> > parent to borrow from... Or maybe their level matters?
>
> In both cases DRR is used to cycle classes to dequeue - this gives us
> fairness (weighted by "quantums").
>
> > I also think that:
> > 1. Until all leaf classes' rate is met we even do not check anything else
> > (including ceil of parent classes)
>
> correct
>
> > 2. the root queue is unlimited feed for the classes which are attached to
> > it directly
>
> yes
>
> > One think I do not understand neither for SFQ nor for HTB (please explain
> > for both) - how can we maintain fairness in case of differently-sizes
> > packets. As I understand, one packet is atomic unit, and interface is
> > requesting not more and not less than one packet. Now given a quantum for
> > each leaf class in HTB or the same for SQF (are they different in this
> > process?) of 1500 bytes - do they wait for more packets from one subclass
> > (asking it once again in the next turn, of course, if they have nothing
> > to send, we switch to the next...)? And if one subclass is providing 1500
> > packets in each turn, and another subclass is providing 800-byte packets
> > - will they be equal on the amount of traffic they are allowed to send in
> > case the real channel is smaller than the sum of their effective ceil
> > values?
>
> both SFQ and HTB (and CBQ) uses DRR which uses BYTES as count not packets.
> Look into literature for "leaky bucket" description. To answer your last
> mail, cannonical HTB theory (v.3 = latest one) is:
> http://luxik.cdi.cz/~devik/qos/htb/manual/theory.htm. It is up to date -
> mainly because algorithm is the same since 2002.
>
> > (I am preparing for a seminar in which I will tell people how it works,
> > so I need to know this perfectly :))) )
>
> Hmm I have talk at SUCON (http://www.suug.ch/sucon/04/speakers.html#7) so
> that
> I'll need to refresh it too :)
>
> devik
>
> _______________________________________________
> 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/

      parent reply	other threads:[~2004-06-16 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-12 11:46 [LARTC] HTB theory? Dmitry Golubev
2004-06-12 12:39 ` Stef Coene
2004-06-12 17:43 ` Dmitry Golubev
2004-06-13 15:23 ` Andy Furniss
2004-06-13 18:41 ` Martin Devera
2004-06-16 15:31 ` Dmitry Golubev [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=200406161831.44991.dmitry@mikrotik.com \
    --to=dmitry@mikrotik.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.