Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: ISN Support Staff <support@isn.net>
To: lartc@vger.kernel.org
Subject: [LARTC] High Latency With Tiered Queues
Date: Fri, 18 May 2007 05:08:12 +0000	[thread overview]
Message-ID: <1179464892.13716.12.camel@eliza> (raw)

Hello,

  I'm trying to setup what I thought would be a fairly basic tiered
shaping system.  I have a 6mbit (768kbps) link coming into my eth1
device, with my LAN IPs on the eth0 device.  I want to limit outgoing
traffic so that certain IPs are limited to 400kbps, with 3 classes under
that 400k so certain machines get prioritized (main servers in 1:21,
other servers in 1:22, workstations in 1:23)

  The problem is that when I turn this on, my packet latency jumps up by
50 to 100 times the normal rate.  I go from 10-20 ms ping times to
500-1600ms!  I've tried putting SFQ qdiscs under the classes, but that
makes no difference.

  I'm sure there is just some tuning parameter I'm not setting
correctly, but can somebody clue me in to what I'm doing wrong?  Or is
HTB just the wrong scheduler to be using here?  I tried CBQ, but I can't
get the tiers to work ( I keep getting RTNETLINK answers: Invalid
argument)  I'm currently using a single tiered CBQ solution, but it
really doesn't fit my needs.

Here's the full script:
-----------------------
qdisc add dev eth1 root handle 1: htb default 10
class add dev eth1 parent 1: classid 1:1 htb rate 768kbps
class add dev eth1 parent 1: classid 1:10 htb rate 250kbps ceil 768kbps
burst 6k
class add dev eth1 parent 1: classid 1:20 htb rate 100kbps ceil 400kbps
burst 6k
class add dev eth1 parent 1:20 classid 1:21 htb rate 75kbps ceil 375kbps
burst 6k
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.35 flowid 1:21
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.29 flowid 1:21
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.28 flowid 1:21
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.16 flowid 1:21
class add dev eth1 parent 1:20 classid 1:22 htb rate 15kbps ceil 350kbps
burst 6k
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.30 flowid 1:22
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.31 flowid 1:22
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.32 flowid 1:22
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.36 flowid 1:22
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.39 flowid 1:22
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.40 flowid 1:22
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.47 flowid 1:22
class add dev eth1 parent 1:20 classid 1:23 htb rate 10kbps ceil 200kbps
burst 6k
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.33 flowid 1:23
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.34 flowid 1:23
filter add dev eth1 parent 1: protocol ip prio 16 u32 match ip src
192.168.1.37 flowid 1:23


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

             reply	other threads:[~2007-05-18  5:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18  5:08 ISN Support Staff [this message]
2007-05-30 20:34 ` [LARTC] High Latency With Tiered Queues Andy Furniss

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=1179464892.13716.12.camel@eliza \
    --to=support@isn.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