All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] About HFSC ?
Date: Thu, 14 Dec 2006 22:15:15 +0000	[thread overview]
Message-ID: <4581CCF3.4000602@andyfurniss.entadsl.com> (raw)
In-Reply-To: <457F18E2.5090208@wanadoo.fr>

Sébastien CRAMATTE wrote:
> Hello,
> 
> I’ve read this Article avout VOIP and HFSC
> http://automatthias.wordpress.com/2006/06/30/hfsc-and-voip/
> 
> I’ve got few questions ?
> 
> Considering this
> 
> tc class add dev $DEV parent 1:1 classid 1:2 hfsc \
> rt m1 ${UPLINK}kbit d 50ms m2 $[1*$UPLINK/10]kbit \
> ls m1 ${UPLINK}kbit d 50ms m2 $[3*$UPLINK/10]kbit \
> ul rate ${UPLINK}kbit

That command and the script look a bit iffy to me - but then I could be 
wrong and often am :-)

> 
> rt = realtime curve
> ls = linksharing curve
> 
> but
> m1 = ?

m1 = slope/rate of the first part of the curve.

> m2 = ?

m2 = slope/rate of the second part.

> d = dmax ?

I think they will be equal if m1>m2, but not if m1<m2. dmax is a time 
when used with umax bytes hfsc will calculate the m1 bitrate needed to 
send a packet umax bytes long with a delay of dmax. d is the point on 
the x axis where m1 ends and m2 starts. If m1<m2 then d is still d but 
not the same as dmax.

Look at the curves on p10 of the sigcom pdf - I think xi = d
http://trash.net/~kaber/hfsc/SIGCOM97.pdf

You can use either format with linux, when you do tc -s -d class ls ... 
the output will be in m1 d m2 format.

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

      reply	other threads:[~2006-12-14 22:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 21:02 [LARTC] About HFSC ? Sébastien CRAMATTE
2006-12-14 22:15 ` 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=4581CCF3.4000602@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.