All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to get the latency down on maxed out classes? + extra question
Date: Tue, 10 Dec 2002 20:55:14 +0000	[thread overview]
Message-ID: <marc-lartc-103955380927068@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103955243525543@msgid-missing>

> TC_UPLINK_RATE="100"
> TC_RATE[0]=50
> TC_CEIL[0]=110
So this class has ceil = 110kbit, but the parent class has ceil = 100kbit.  
The parent ceil is not respected so this class can use 110kbit if it wants.  
I don't think this is what you want.

> TC_RATE[1]=15
> TC_CEIL[1]=60
> TC_RATE[2]=10
> TC_CEIL[2]=60
> TC_RATE[3]=5
> TC_CEIL[3]=30
There is also a drawbeck if you use prio to improve latency.  Devik did some 
testing.  A lower prio is good for delays IF the class with the lower prio 
never sends more then it's rate (so it's never overlimited).  If it do so, 
other classes are served first and the delays will be very bad.  I haven't 
test it myself, but you can find it in the user guide of htb chapter 7 
(http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm#prio).
You can force a class to never exceeds its rate if you use a policer in the 
filter so packets that exceeds the rate are dropped by the filter.  But 
again, I haven't test it.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

  reply	other threads:[~2002-12-10 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 20:32 [LARTC] how to get the latency down on maxed out classes? + extra question sufcrusher
2002-12-10 20:55 ` Stef Coene [this message]
2002-12-11  0:57 ` sufcrusher
2002-12-11 12:35 ` 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-103955380927068@msgid-missing \
    --to=stef.coene@docum.org \
    --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.