All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB Rate and Prio (continued)
Date: Mon, 11 Jul 2005 18:44:40 +0000	[thread overview]
Message-ID: <42D2BE18.5010407@dsl.pipex.com> (raw)
In-Reply-To: <200507111126.j6BBQT5t007024@dhuumrelay0.mail.eu.uu.net>

Gael Mauleon wrote:
> Hi again,
> 
>  
> 
> I keep posting about my problem with HTB ->
> http://mailman.ds9a.nl/pipermail/lartc/2005q3/016611.html

I had a go with what you posted there over lan and with 2 tcp streams it 
behaves as expected (see below for exact test).

Can you reproduce the failiure shaping over a lan rather than your 
internet connection?

If your upstream bandwidth is sold as 2meg then ceil 2000kbit is likely 
to be too high.

You could also try specifying quantum = 1500 on all the leafs as you get 
it auto calculated from rates otherwise (you can see them with tc -s -d 
class ls ...). It didn't affect my test though.

If you are looking at htbs rate counters remember that they use a really 
long average (about 100 sec) so they can mislead.

I tested below with two netperf tcp send tests to ips I added to another 
  PC on my lan.

# /usr/local/netperf/netperf -H 192.168.0.60 -f k -l 60 & 
/usr/local/netperf/netperf -f k -H 192.168.0.102 -l 60 &

which gave -

Recv   Send    Send
Socket Socket  Message  Elapsed
Size   Size    Size     Time     Throughput
bytes  bytes   bytes    secs.    10^3bits/sec

  43689  16384  16384    60.09    1884.66
Recv   Send    Send
Socket Socket  Message  Elapsed
Size   Size    Size     Time     Throughput
bytes  bytes   bytes    secs.    10^3bits/sec

  43689  16384  16384    60.22      51.58


The script -

QOSIN=eth0

tc qdisc del dev $QOSIN root &>/dev/null

tc qdisc add dev $QOSIN root handle 1:0 htb
tc class add dev $QOSIN parent 1:0 classid 1:1 htb rate 2000kbit

### SUBCLASS1

tc class add dev $QOSIN parent 1:1 classid 1:10 htb rate 750kbit ceil 
2000kbit prio 1

tc class add dev $QOSIN parent 1:10 classid 1:101 htb rate 250kbit ceil 
2000kbit prio 1

tc qdisc add dev $QOSIN parent 1:101 handle 101: pfifo limit 10

tc class add dev $QOSIN parent 1:10 classid 1:102 htb rate 250kbit ceil 
2000kbit prio 1

tc qdisc add dev $QOSIN parent 1:102 handle 102: pfifo limit 10

tc class add dev $QOSIN parent 1:10 classid 1:103 htb rate 250kbit ceil 
2000kbit prio 1

tc qdisc add dev $QOSIN parent 1:103 handle 103: pfifo limit 10

tc filter add dev $QOSIN parent 1:0 protocol ip u32 match ip dst 
192.168.0.102 flowid 1:102

###HIGH PRIO ###

tc class add dev $QOSIN parent 1:1 classid 1:50 htb rate 50kbit ceil 
2000kbit prio 0 quantum 1500

tc qdisc add dev $QOSIN parent 1:50 handle 50: pfifo limit 10

### LOW PRIO ###

tc class add dev $QOSIN parent 1:1 classid 1:60 htb rate 50kbit ceil 
2000kbit prio 5 quantum 1500

tc qdisc add dev $QOSIN parent 1:60 handle 60: pfifo limit 10

tc filter add dev $QOSIN parent 1:0 protocol ip u32 match ip dst 
192.168.0.60 flowid 1:60


Andy.

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

  reply	other threads:[~2005-07-11 18:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 11:27 [LARTC] HTB Rate and Prio (continued) Gael Mauleon
2005-07-11 18:44 ` Andy Furniss [this message]
2005-07-12 12:08 ` Gael Mauleon
2005-07-13 10:25 ` Gael Mauleon
2005-07-13 10:34 ` Gael Mauleon
2005-07-13 22:15 ` Andy Furniss
2005-07-13 22:26 ` Andy Furniss
2005-07-13 22:47 ` Andy Furniss
2005-07-15  8:24 ` Gael Mauleon
2005-07-15 10:26 ` Gael Mauleon

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=42D2BE18.5010407@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.