Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Mark Williams (MWP)" <mwp@internode.on.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Weighted packet shaping?
Date: Sun, 26 Dec 2004 04:38:49 +0000	[thread overview]
Message-ID: <20041226042648.GA24904@linux.comp> (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.
> >>>
> >>><snip>
> >>
> >>
> >>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.
> >
> >
> >Ok, im now trying:
> >
> >class add dev $INTERFACE parent 1: classid 1:1 htb rate 220kbit
> >class add dev $INTERFACE parent 1:1 classid 1:20 htb rate 70kbit ceil 
> >220kbit prio 1
> >class add dev $INTERFACE parent 1:1 classid 1:21 htb rate 50kbit ceil 
> >220kbit prio 2
> >class add dev $INTERFACE parent 1:1 classid 1:22 htb rate 25kbit ceil 
> >220kbit prio 3
> >class add dev $INTERFACE parent 1:1 classid 1:23 htb rate 25kbit ceil 
> >220kbit prio 4
> >class add dev $INTERFACE parent 1:1 classid 1:24 htb rate 25kbit ceil 
> >220kbit prio 5
> >class add dev $INTERFACE parent 1:1 classid 1:25 htb rate 25kbit ceil 
> >220kbit prio 8
> >
> >Its simply not working.
> >Bittorrent is using ~22kb/sec on class 25, leaving the FTP upload (class 
> >22)
> >sitting on only ~3kb/sec.
> >
> >Any ideas? 
> 
> 
> Are you sure that FTP is going to class 22 and not default -
> 
> tc -s qdisc ls dev $INTERFACE or tc -s class ls dev $INTERFACE will show 
> counters.

I am.
I graph using "tc -s qdisc show dev ppp0" with rrdtool.

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

  parent reply	other threads:[~2004-12-26  4:38 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
2004-12-24 15:19 ` Mark Williams (MWP)
2004-12-24 16:36 ` Andy Furniss
2004-12-26  4:38 ` Mark Williams (MWP) [this message]
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=20041226042648.GA24904@linux.comp \
    --to=mwp@internode.on.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