From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb vs hsfc
Date: Fri, 25 Jun 2004 01:51:04 +0000 [thread overview]
Message-ID: <40DB8508.6060001@trash.net> (raw)
In-Reply-To: <40DB0D84.8050603@club-internet.fr>
Vincent Perrier wrote:
> HTB versus HFSC, both qdisc offer the same kind of service,
> if you want to see comparative test results, go to
> http://www.rawsoft.org
> at the line "TEST RESULTS" you will find the results for
> a sharing test and a burst test.
> You will see that both qdisc are good.
Nice comparision, very interesting. Note that you have a small
misconfiguration in your HFSC setup. On page 8 you say "The
shaping is impacted by real time bursts". This is only because
your real-time classes are not part of the link-sharing hierarchy.
If you add link-share curves to the real-time classes which are
equal to the real-time curves shaping won't be impacted.
Regards
Patrick
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-06-25 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 17:21 [LARTC] htb vs hsfc Vincent Perrier
2004-06-24 20:21 ` Jason Boxman
2004-06-25 1:51 ` Patrick McHardy [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=40DB8508.6060001@trash.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox