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] Weighted packet shaping?
Date: Fri, 24 Dec 2004 14:08:49 +0000	[thread overview]
Message-ID: <41CC22F1.70907@dsl.pipex.com> (raw)
In-Reply-To: <20041221034303.GB27656@linux.comp>

Mark Williams (MWP) wrote:

>>For now try making a parent with rate and ceil 220kbit.
>>Have 4 child/leaf classes like - (assuming 1 is highest priority)
>>
>>class 1 rate 120 ceil 220 prio 0
>>class 2 rate 50 ceil 220 prio 1
>>class 3 rate 25 ceil 220 prio 2
>>class 4 rate 25 ceil 220 prio 3
>>
>>There are other tweaks you can try, it depends how much you care about 
>>latency. You could also share the windows boxes bandwidth by IP.
>>
>>I don't do it quite like the above - so if it doesn't work, say and I'll 
>>think again.
> 
> 
> Well im currently using:
> 
>     #root device
>     $TC qdisc add dev $INTERFACE root handle 1: htb default 25
> 
>     #root class
>     $TC class add dev $INTERFACE parent 1: classid 1:1 htb rate 256kbit
> 
>     #20 - ICMP, DNS, SYN, SSH
>     $TC class add dev $INTERFACE parent 1:1 classid 1:20 htb rate 128kbit ceil 256kbit prio 1
>     $TC qdisc add dev $INTERFACE parent 1:20 handle 20: sfq perturb 10
>     $TC filter add dev $INTERFACE parent 1:0 prio 0 protocol ip handle 20 fw flowid 1:20
> 
>     #21 - HTTP/FTP out
>     $TC class add dev $INTERFACE parent 1:1 classid 1:21 htb rate 128kbit ceil 256kbit prio 2
>     $TC qdisc add dev $INTERFACE parent 1:21 handle 21: sfq perturb 10
>     $TC filter add dev $INTERFACE parent 1:0 prio 0 protocol ip handle 21 fw flowid 1:21
> 
>     #22 - All cool.comp traffic
>     $TC class add dev $INTERFACE parent 1:1 classid 1:22 htb rate 128kbit ceil 256kbit prio 3
>     $TC qdisc add dev $INTERFACE parent 1:22 handle 22: sfq perturb 10
>     $TC filter add dev $INTERFACE parent 1:0 prio 0 protocol ip handle 22 fw flowid 1:22
> 
>     #23 - All ian.comp traffic
>     $TC class add dev $INTERFACE parent 1:1 classid 1:23 htb rate 64kbit ceil 256kbit prio 4
>     $TC qdisc add dev $INTERFACE parent 1:23 handle 23: sfq perturb 10
>     $TC filter add dev $INTERFACE parent 1:0 prio 0 protocol ip handle 23 fw flowid 1:23
> 
>     #24 - HTTP/FTP in
>     $TC class add dev $INTERFACE parent 1:1 classid 1:24 htb rate 64kbit ceil 256kbit prio 5
>     $TC qdisc add dev $INTERFACE parent 1:24 handle 24: sfq perturb 10
>     $TC filter add dev $INTERFACE parent 1:0 prio 0 protocol ip handle 24 fw flowid 1:24
> 
>     #25 - Everything else
>     $TC class add dev $INTERFACE parent 1:1 classid 1:25 htb rate 20kbit ceil 64kbit prio 8
>     $TC qdisc add dev $INTERFACE parent 1:25 handle 25: sfq perturb 10
>     $TC filter add dev $INTERFACE parent 1:0 prio 0 protocol ip handle 25 fw flowid 1:25


Try to make it look like I said - back off from 256 ceil, make rates add 
up to master rate (220), give interactive more rate than it will ever need.

Class 24 does not make sense to me, and you may also find that ftp goes 
to default - It can be hard to mark and I can't see how you are marking it.

Andy.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-12-24 14:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21  3:55 [LARTC] Weighted packet shaping? Mark Williams (MWP)
2004-12-22  4:53 ` Mark Williams (MWP)
2004-12-22  9:07 ` Ed Wildgoose
2004-12-22 13:49 ` Andy Furniss
2004-12-22 15:48 ` Mark Williams (MWP)
2004-12-22 22:54 ` Andy Furniss
2004-12-23 10:56 ` Mark Williams (MWP)
2004-12-24 14:08 ` Andy Furniss [this message]
2004-12-24 15:19 ` Mark Williams (MWP)
2004-12-24 16:36 ` Andy Furniss
2004-12-26  4:38 ` Mark Williams (MWP)
2004-12-26 13:09 ` Andy Furniss
2004-12-28  9:35 ` Mark Williams (MWP)
2004-12-29  2:46 ` Andy Furniss
2004-12-29  6:52 ` Mark Williams (MWP)
2004-12-29 13:26 ` Francisco Pereira
2004-12-30  0:05 ` Andy Furniss
2005-01-03 11:22 ` marco ghidinelli
2005-01-04 13:57 ` 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=41CC22F1.70907@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.