All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Simo" <simo@mix4web.de>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] PRIO and TBF is much better than HTB??
Date: Fri, 11 May 2007 08:36:31 +0000	[thread overview]
Message-ID: <001501c793a7$7c3d4480$74b7cd80$@de> (raw)
In-Reply-To: <001401c79315$b1732c60$14598520$@de>


[-- Attachment #1.1: Type: text/plain, Size: 1117 bytes --]

Hi,

Thanks for your answer.

You are right concerning the PRIO QDisc, but which I did not understand is
that the combination (PRIO+TBF) made a Shaping nearly exactly the same as
with HTB only with better latency. One sees this with the comparison of the
two following illustrations of my simulation: 
HTB with prio parameter cumulative:
http://simo.mix4web.de/up/htb_cumul_prio_paramter.jpg
PRIO and TBF cumulative: http://simo.mix4web.de/up/prio_tbf_cumul.jpg

>
> theory it will even starve the low priority traffic, if high prio traffic
is waiting to go out.
>


In the first illustration you can see that  the low priority traffic also
has been served (nearly exactly the same as with HTB). Because of the use of
PRIO in combination with TBF.

But the latency is much better, if you compares the following illustrations:

HTB with prio parameter delay:
http://simo.mix4web.de/up/htb_delay_prio_parameter.jpg
PRIO and TBF delay: http://simo.mix4web.de/up/prio_tbf_delay.jpg

I think that the overhead with the HTB algorithm is larger and the scheduler
keeps the packets a little longer in the queues.

Simo



 


[-- Attachment #1.2: Type: text/html, Size: 4386 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-05-11  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 15:12 [LARTC] PRIO and TBF is much better than HTB?? Simo
2007-05-11  6:25 ` Salim S I
2007-05-11  8:36 ` Simo [this message]
2007-05-11  9:18 ` Salim S I
2007-05-11  9:40 ` Andy Furniss
2007-05-11 11:53 ` Simo
2007-05-11 15:50 ` Flechsenhaar, Jon J

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='001501c793a7$7c3d4480$74b7cd80$@de' \
    --to=simo@mix4web.de \
    --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.