All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] beta-release of H-FSC port for Linux 2.6
Date: Sat, 01 Nov 2003 14:45:04 +0000	[thread overview]
Message-ID: <marc-lartc-106770119405900@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106719267625234@msgid-missing>

Hi Torsten,

Griem, Hans T wrote:

>I read the abstract and introduction to original H-FSC paper.  I believe it was mostly about decoupling bw and delay.
>It seems to me HTB does this well.  When and/or why would I would want to use H-FSC versus HTB or are they direct competitors?
>  
>
Not sure what you mean with "competitors", I made this port for
fun after happily discovering that the code was very nicely
written (unlike the version mentioned in the paper). This should
not be understood as dissatisfaction with HTB, I was perfectly
happy with the entire time I used it.

So why would you want to use H-FSC .. you're right, a major
feature of H-FSC is decoupling of bandwidth and delay, but it
also offers delay _guarantees_ if configured correctly. This is
very important for streaming, VoIP, .. (and gamers of course).
I don't know if my understanding of HTB's algorithm is correct,
but it is basically a chained token bucket, so delay is directly
coupled to bandwidth. Also I believe it always tries to dequeue
"quantum" bytes at once so classes might go overlimits for a
limited period of time. This hurts delay. On the other hand,
HTB is more expressive due to priorites. So I'd say it basically
comes down to expressiveness vs. delay guarantees. However
I was able to convert my HTB config to something very similar
with H-FSC depite using priorites with HTB.

I hope that anwers your question.

Best regards,
Patrick



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

  parent reply	other threads:[~2003-11-01 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26 18:04 [LARTC] beta-release of H-FSC port for Linux 2.6 Patrick McHardy
2003-11-01  0:56 ` Griem, Hans T
2003-11-01 14:45 ` Patrick McHardy [this message]
2003-11-01 21:09 ` Thilo Schulz
2003-11-03  9:18 ` Alexey Sheshka
2003-11-04 14:19 ` Patrick McHardy
2003-11-13  9:49 ` Cezar Atanasiu

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-106770119405900@msgid-missing \
    --to=kaber@trash.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 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.