Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Homer Parker <hparker@homershut.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How HTB treats priorities?
Date: Thu, 02 Jan 2003 16:26:20 +0000	[thread overview]
Message-ID: <marc-lartc-104152484511959@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104110872106366@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]

On Tue, 31 Dec 2002 00:37:44 +0100 Stef Coene <stef.coene@docum.org>
wrote....

> > Lets assume all classes try to send at their maximum speed trying to
> > saturate the link. According to what you have written class D will get
> > 64kbit/s, class E 128kbit/s and class F will get 32kbit/s. The sum is
> > 224kbit/s if I am correct. Am I right?
> Yes.  So the rate of the parent B must also be at least 224kbit/s.  And
> not 8kbis/s like you wrote before.
> 
> > I dont want it to happen since customers have paid for 128kbit/s with
> > guaranteed rato of 8kbit/s. Is there a way to acomplish my task???.
> > Can it be done using HTB only?
> Yes, make the sum of D,E and F = 128kbit/s.

	This is the same kind of setup I've been shooting for. When you say the
sum of D, E and F, are you talking rate or ceil? I would imagine ceil.
That makes it hard to please the customer who is paying for 128kbit, yet
only sees it in 3 42kbit streams, or some other breakdown of the 128k. If
I understand you right, there is no way to run three seperate children for
prioritizing packets, and still give full bandwidth of parent to any of
the three, without allowing the use of all three at the same time to
exceed the parent?

--- 
Homer Parker                  /"\ ASCII Ribbon Campaign
                              \ / No HTML/RTF in email
http://www.homershut.net       x  No Word docs in email
telnet://bbs.homershut.net    / \ Respect for open standards

This e-mail message is 100% Microsoft free!

WARNING: THIS ACCOUNT BELONGS TO A RABID
ANTI-SPAMMER NET-NAZI DOT-COMMUNIST!!


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-01-02 16:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28 20:53 [LARTC] How HTB treats priorities? ISC Robert Kryczało
2002-12-29  5:01 ` Stephane Ouellette
2002-12-29 23:23 ` Stef Coene
2002-12-30 22:35 ` ISC Robert Kryczało
2002-12-30 23:37 ` Stef Coene
2003-01-02 16:26 ` Homer Parker [this message]
2003-01-02 17:56 ` ISC Robert Kryczało
2003-01-02 18:03 ` ISC Robert Kryczało
2003-01-02 21:57 ` Stef Coene
2003-01-04 20:21 ` ISC Robert Kryczało
2003-01-05 17:42 ` Stef Coene
2003-01-06 18:54 ` ISC Robert Kryczało
2003-01-06 19:32 ` 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-104152484511959@msgid-missing \
    --to=hparker@homershut.net \
    --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