All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB - prio and rate
Date: Sat, 03 Dec 2005 23:14:44 +0000	[thread overview]
Message-ID: <1133651687.25718.19.camel@pc.local> (raw)
In-Reply-To: <BF782D07436CAE4B931BFA5B2C68FF4F0F8E44@bmts1.ad.bmtseatech.co.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1674 bytes --]

I really don't seem to be getting this.  ~sigh~

As I wrote before I'm not interested in dividing bandwidth up, just
prioritizing the use of the full bandwidth by all-comers.

So I figure I want a TBF in my root class to prevent the queue in my DSL
modem from filling up.  I have about 128kb/s upstream so I added:

# tc qdisc add dev ppp0 root handle 1: tbf rate 120kbit latency 50ms burst 1540

(not sure what values I want for latency and burst)

Then I figure I want a PRIO classifier with 3 bands.  I want anything
not otherwise matching a filter to go in band 2, known bulk to go in
band 3 and priority, latency sensitive "interactive" stuff (i.e. ssh,
not scp) to go in band 1:

# tc qdisc add dev ppp0 parent 1: handle 10: prio

And then only because some examples showed using it, I put an SFQ in
each band.  Do I really need this?  Should I not do this step?

# tc qdisc add dev ppp0 parent 10:1 handle 100: sfq
# tc qdisc add dev ppp0 parent 10:2 handle 200: sfq
# tc qdisc add dev ppp0 parent 10:3 handle 300: sfq

Now I want to use iptables to put stuff into the different bands.
Again, by example I have been trying to do some iptables rules with -j
CLASSIFY --set-class (this one to get ping to be processed in the
highest priority band to test the effectiveness of "interactive
traffic):

# iptables -t mangle -I POSTROUTING -p icmp --icmp-type echo-request -j CLASSIFY --set-class 10:100

I'm not sure what the class numbers I should be using.  Would they be
10:100, 10:200 and 10:300 for the 3 bands?  or 10:1, 10:2 and 10:3?

Thanx,
b.

-- 
My other computer is your Microsoft Windows server.

Brian J. Murrell

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

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

  parent reply	other threads:[~2005-12-03 23:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 13:57 [LARTC] HTB - prio and rate Mark Lidstone
2005-12-02 20:25 ` Andreas Klauer
2005-12-02 20:31 ` Brian J. Murrell
2005-12-02 20:48 ` Andreas Klauer
2005-12-02 22:24 ` Brian J. Murrell
2005-12-03  6:04 ` Andreas Klauer
2005-12-03 23:14 ` Brian J. Murrell [this message]
2005-12-04  2:32 ` Jeffrey B. Ferland
2005-12-04  3:17 ` Jason Boxman
2005-12-04  3:26 ` Jason Boxman
2005-12-04  6:24 ` Andreas Klauer
2005-12-04 13:48 ` Brian J. Murrell
2005-12-04 15:14 ` Jeffrey B. Ferland
2005-12-04 16:05 ` Brian J. Murrell
2005-12-05  9:40 ` Mark Lidstone
2005-12-05 18:15 ` Andreas Klauer
2005-12-06 12:27 ` Mark Lidstone
2005-12-13  8:51 ` Mark Lidstone

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=1133651687.25718.19.camel@pc.local \
    --to=brian@interlinx.bc.ca \
    --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.