From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] QoS for VoIP
Date: Fri, 28 Sep 2007 01:09:20 +0000 [thread overview]
Message-ID: <009801c8016c$332e7ec0$0100a8c0@MingChing> (raw)
In-Reply-To: <marc-lartc-107000832316611@msgid-missing>
From: "Santiago" <santiago@elportal.net.ec>
> The prio qdisc is the solution. Try this.
>
I wonder if that's speaking from experience or speaking from
theoretical standpoint ? I have always been told, to control
the traffic, I have to be the slowest link in the chain.
And my question is how slow I should be ! If you are
not the slowest, you can't control. If you are damn slow,
you are under-utilizing your bandwidth.
Read this section of LARTC :-
http://lartc.org/howto/lartc.qdisc.html
You also have to be sure you are controlling the bottleneck of the link. If
you have a 100Mbit NIC and you have a router that has a 256kbit link, you
have to make sure you are not sending more data than your router can handle.
Otherwise, it will be the router who is controlling the link and shaping the
available bandwith. We need to 'own the queue' so to speak, and be the
slowest link in the chain. Luckily this is easily possible.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-09-28 1:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 8:12 [LARTC] QoS for VoIP Craig Main
2003-11-28 18:05 ` Kilian Krause
2007-09-27 2:31 ` Ming-Ching Tiew
2007-09-27 16:05 ` Santiago
2007-09-28 1:09 ` Ming-Ching Tiew [this message]
2007-09-28 2:45 ` Santiago
2007-09-28 14:07 ` Santiago
2007-10-01 1:00 ` Ming-Ching Tiew
-- strict thread matches above, loose matches on Subject: below --
2004-07-16 15:19 [LARTC] QoS for Voip Alessandro Ren
2004-07-16 15:53 ` Andreas Klauer
2004-07-16 16:54 ` Jason Boxman
2004-07-16 17:51 ` ibro tj
2004-07-16 18:38 ` Andreas Klauer
2004-07-19 12:45 ` Alessandro Ren
2004-07-19 13:19 ` Andreas Klauer
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='009801c8016c$332e7ec0$0100a8c0@MingChing' \
--to=mingching.tiew@redtone.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.