All of lore.kernel.org
 help / color / mirror / Atom feed
From: sophana <sophana78@yahoo.fr>
To: lartc@vger.kernel.org
Subject: [LARTC] max latency with htb and wondershaper for voip and p2p
Date: Thu, 24 Nov 2005 21:10:36 +0000	[thread overview]
Message-ID: <43862C4C.4060104@yahoo.fr> (raw)

Hi

I'm actually using a wondershaper derived script.
The problem I have is that when I ping (ping is in high priority queue)
the ping time is not as low as I expected with p2p running:

760 packets transmitted, 760 received, 0% packet loss, time 759695ms
rtt min/avg/max/mdev = 39.667/62.863/598.539/33.287 ms, pipe 2

With voip, it is much better with the qos but it is still a little choppy.

My line is an adsl 512/128 kbit/s. Assuming the biggest low prio packet 
is about 1.5kbyte, this makes a max latency of 93ms higher than min 
latency: 133ms in my case. (that's what I notice on the ping times)

I don't understand why is voip still choppy.

In my config, can I assume that packets in 1:10 have the highest 
priority even with htb? (if the 1:10 rate is not reached).
Do I need to setup a prio qdisc instead of htb for voip?
If I lower the mtu of the p2p software to 750byte for example, will I 
get a max latency of 87ms?
Can I do voip and P2P together with htb with such a line?
Thanks for your help.


     qdisc htb 1: r2q 1 default 20 direct_packets_stat 0
qdisc htb 1:      :       9637 ( 77.096000 kbit/s) sent05656509  :
      Sent 305656509 bytes 1228041 pkts (dropped 0, overlimits 559094 
requeues 0)
     qdisc sfq 10: parent 1:10 limit 128p quantum 1514b perturb 10sec
qdisc sfq 10:     :        588 (  4.704000 kbit/s) sent(498626  :
      Sent 28498626 bytes 489927 pkts (dropped 0, overlimits 0 requeues 0)
     qdisc sfq 20: parent 1:20 limit 128p quantum 1514b perturb 10sec
qdisc sfq 20:     :        228 (  1.824000 kbit/s) sent‚88143  :
      Sent 8288143 bytes 81245 pkts (dropped 0, overlimits 0 requeues 0)
     qdisc sfq 30: parent 1:30 limit 128p quantum 1514b perturb 10sec
qdisc sfq 30:     :       8821 ( 70.568000 kbit/s) sent&8869740  :
      Sent 268869740 bytes 656869 pkts (dropped 0, overlimits 0 requeues 0)
     qdisc ingress ffff: ----------------
qdisc ingress ffff: :       7005 ( 56.040000 kbit/s) sent\x127032425  :
      Sent 127032425 bytes 1036821 pkts (dropped 52, overlimits 0 
requeues 0)
     class htb 1:1 root rate 110Kbit ceil 110Kbit burst 1612b cburst 1612b
class htb 1:1     :       9637 ( 77.096000 kbit/s) sent05656509  :
      Sent 305656509 bytes 1228041 pkts (dropped 0, overlimits 0 requeues 0)
      rate 7480bit 29pps
      lended: 400601 borrowed: 0 giants: 0
      tokens: 116551 ctokens: 116551

     class htb 1:10 parent 1:1 leaf 10: prio 0 rate 55Kbit ceil 110Kbit 
burst 6Kb cburst 1612b
class htb 1:10    :        588 (  4.704000 kbit/s) sent(498626  :
      Sent 28498626 bytes 489927 pkts (dropped 0, overlimits 0 requeues 0)
      rate 715bit 12pps
      lended: 489927 borrowed: 0 giants: 0
      tokens: 907972 ctokens: 116551

     class htb 1:20 parent 1:1 leaf 20: prio 1 rate 33Kbit ceil 110Kbit 
burst 1603b cburst 1612b
class htb 1:20    :        228 (  1.824000 kbit/s) sent‚88143  :
      Sent 8288143 bytes 81245 pkts (dropped 0, overlimits 0 requeues 0)
      rate 133bit 1pps
      lended: 80319 borrowed: 926 giants: 0
      tokens: 378446 ctokens: 116551

     class htb 1:30 parent 1:1 leaf 30: prio 2 rate 22Kbit ceil 110Kbit 
burst 1601b cburst 1612b
class htb 1:30    :       8821 ( 70.568000 kbit/s) sent&8869740  :
      Sent 268869740 bytes 656869 pkts (dropped 0, overlimits 0 requeues 0)
      rate 6686bit 15pps
      lended: 257194 borrowed: 399675 giants: 0
      tokens: 101987 ctokens: 104038



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

                 reply	other threads:[~2005-11-24 21:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=43862C4C.4060104@yahoo.fr \
    --to=sophana78@yahoo.fr \
    --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.