From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] English translation of article on HFSC
Date: Sat, 24 Jun 2006 12:34:48 +0000 [thread overview]
Message-ID: <449D3168.7040302@andyfurniss.entadsl.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0606230758050.30090@solidus.wonderfrog.net>
Martin A. Brown wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Greetings all,
>
> Working in concert with the original authors, Klaus Rechert and
> Patrick McHardy, I have translated their article "HFSC Scheduling
> mit Linux" [0] on Hierarchical Fair Service Curve (HFSC) into
> English [1].
Thanks Martin.
>
> http://linux-ip.net/tc/hfsc.en/
I don't claim to totally get hfsc and don't actually use it yet because
until recently I only had 288kbit upstream at atm level, which doesn't
leave enough to split 4/5 users equally. I have 448 now so will use it
soon, especially if there is going to be a proper atm overhead accounting.
I did in the past test a 4/5 way equal user setup and what I saw makes
me curious why all the classes in the example are sc.
From the tests I did the nice thing about hfsc is that you can have 5
backlogged ls classes and still only add jitter from the transmit time
of one mtu packet. HTB will add 5x in this case but it's jitter and you
can skew the average a bit.
5 backlogged/near rate rt with MTU sized packets = 5x jitter with hfsc
so rt really needs to be uses carefully ?
Of course I havent re tested - it may have been because the ls each had
very small rates but could borrow.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-06-24 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 13:37 [LARTC] English translation of article on HFSC Martin A. Brown
2006-06-23 14:41 ` Nickola Kolev
2006-06-23 15:27 ` Martin A. Brown
2006-06-23 15:44 ` Patrick McHardy
2006-06-24 12:34 ` Andy Furniss [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=449D3168.7040302@andyfurniss.entadsl.com \
--to=lists@andyfurniss.entadsl.com \
--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.