From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC parameter
Date: Tue, 26 Sep 2006 15:14:10 +0000 [thread overview]
Message-ID: <451943C2.3010405@trash.net> (raw)
In-Reply-To: <20060924133900.42854.qmail@web35515.mail.mud.yahoo.com>
Thossapron Apinyapanha wrote:
> tc command's HFSC have a lot parameter with 4 curve type
>
> SC curve -> umax dmax rate
> LS curve -> umax dmax rate
> RT curve -> umax dmax rate
> UL curve -> umax dmax rate
>
> so i'dont know which parameter are appropriate for my test case
> such real time class which curve are appropriate and good working result.
LS = link-share service curve, defines relation of service between
sibling classes. Can be used for intermediate and leaf classes.
UL = upper-limit service curve, limits LS curve.
RS = real-time service curve, defines absolute service guarantees
for leaf classes. Can be used, but does nothing for intermediate
classes.
SC = service curve, sets LS and RS to the same curve. Should usually
be used for leaf-classes instead of RS.
> my assumption about umax,dmax,rate ... this is true
> first, HFSC will doing with "umax" rate but after delay exceed "dmax" rate,
> HFSC will change rate to "rate" ????
No, this is true for m1, d and m2 (use rate m1 for time d, then m2).
umax, dmax and rate are another way to specify the curve, m2 = rate
and m1 and d are calculated from umax and dmax.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-09-26 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 13:39 [LARTC] HFSC parameter Thossapron Apinyapanha
2006-09-25 18:17 ` Konrad Cempura
2006-09-26 15:14 ` 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=451943C2.3010405@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