Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Victor Cassar <victorcassar@yahoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] quantum value for voip
Date: Thu, 13 Feb 2003 16:00:28 +0000	[thread overview]
Message-ID: <marc-lartc-104515209813416@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104509464522905@msgid-missing>

Thanks Stef

Yep i missunderstood the quantum concept (it´s clear
now), but since my voip class was configured with
enough bw this doesn´t matter

Reading more on docum.org, i find hte possible cause
of the delays i was using sfq (128p queue) on the leaf
i removed sfq from the voip class


I will try also with other disciplines.. like tbf
just to have a deeper understanding of queuing in real
life applications

Are there any recomendation on which queuing
discipline to use with voip?
(my stats show 100 bytes per packet average in voip)

i´m doing more tests now and i´ll re re-read the full
lartc. doc

regards



--- Stef Coene <stef.coene@docum.org> wrote:
> On Thursday 13 February 2003 00:59, Victor Cassar
> wrote:
> > Well
> >
> > I understand why quantum should be at least equal
> to
> > mtu size
> >
> > but let´s think in this
> >
> > if i have a dsl link and i want to give more
> quality
> > to
> > "one voip user"
> > i´ve already solved the dsl upload problem
> transfering
> > the bottleneck to my shapping box.
> >
> > Should i change the quantum to a lower value for
> that
> > class?
> >
> > any ideas or comments about this?
> Do you know where quantum is used for?  It's for
> classes that are asking for 
> remaining bandwidth.  So if that "one voip user" is
> never asking for more 
> then the configured rate of its class, quantum is
> never used.  So it really 
> depends on how you configured the classes to answer
> that question.
> 
> And taking a quantum of 10 byte is not "wrong".  But
> if you send 1000byte and 
> your quantum is 10byte, htb will use 10byte in it's
> calculations.  So it can 
> disturb the setup, but nothing bad will happen.
> 
> Stef
> 
> -- 
> 
> stef.coene@docum.org
>  "Using Linux as bandwidth manager"
>      http://www.docum.org/
>      #lartc @ irc.oftc.net
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
http://lartc.org/


__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-02-13 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 23:59 [LARTC] quantum value for voip Victor Cassar
2003-02-13  7:34 ` Stef Coene
2003-02-13 16:00 ` Victor Cassar [this message]
2003-02-13 18:37 ` Stef Coene
2003-02-14  0:13 ` Mathieu Deziel
2003-02-14  0:18 ` Mathieu Deziel
2003-02-14  8:01 ` Stef Coene
2003-02-14 13:38 ` Mathieu Deziel
2003-02-15  2:39 ` Victor Cassar
2003-02-17 13:05 ` Mathieu Deziel

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-104515209813416@msgid-missing \
    --to=victorcassar@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox