All of lore.kernel.org
 help / color / mirror / Atom feed
From: radus <radus@rdsor.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] limiting users on a 128kbit line
Date: Thu, 20 Feb 2003 14:17:37 +0000	[thread overview]
Message-ID: <marc-lartc-104575072331126@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104569091203067@msgid-missing>

Hello!
First, thanks for the reply...

> > 5 computers that get dedicated bandwidth and the rest go in a pool with
> > bigger priorities.
>
> I do not see the priorities in your script.  Only some of the filters have
> priorities, but it has nothing to do with scheduling (you should give
> prioirties to the HTB classes).
>

I made priorities only for the big class where the default traffic goes, so 
that the remaining 5 computers share the bandwidth equally (when it's free)
I should write prios for all classes ?

> You mean it all goes to 1:14 ?

Yes, exactly that....

>
> Quantum = rate/r2q
> For class 1:12, quantum = 10k/r2q = 10*1024(8*r2q) = 1280Bytes.
> This is smaller than MTU, that's why it complains that quantum is too
> small.
>
> Same thing for classes 1:13 and 1:14, quantum = 640 Bytes, which is smaller
> them MTU.
>
> What you can (and should) do is specify the quantum manually.
>
Could you give me an example for a class on how to specify the quantum ?

Radu


> > Here's the script :
> >
> > tc qdisc add dev eth1 root handle 1: htb default 14  r2q 1
> > tc class add dev eth1 parent 1: classid 1:1 htb rate 128kbit burst 2k
> > tc class add dev eth1 parent 1:1 classid 1:10 htb rate 48kbit burst 2k
> >
> > tc class add dev eth1 parent 1:1 classid 1:20 htb rate 12kbit ceil
> > 128kbit burst 2k
> >
> > tc class add dev eth1 parent 1:1 classid 1:30 htb rate 12kbit ceil
> > 128kbit burst 2k
> >
> > tc class add dev eth1 parent 1:1 classid 1:40 htb rate 12kbit ceil
> > 128kbit burst 2k
> >
> > tc class add dev eth1 parent 1:1 classid 1:50 htb rate 12kbit ceil
> > 128kbit burst 2k
> >
> > tc class add dev eth1 parent 1:1 classid 1:11 htb rate 20kbit ceil
> > 128kbit burst 2k
> >
> > tc class add dev eth1 parent 1:11 classid 1:12 htb rate 10kbit  burst 2k
> > tc class add dev eth1 parent 1:11 classid 1:13 htb rate 5kbit   burst 2k
> > tc class add dev eth1 parent 1:11 classid 1:14 htb rate 5kbit   burst 2k
> >
> > tc qdisc add dev eth1 parent 1:20 handle 20:  sfq perturb 15
> > tc qdisc add dev eth1 parent 1:30 handle 30:  sfq perturb 15
> > tc qdisc add dev eth1 parent 1:40 handle 40:  sfq perturb 15
> > tc qdisc add dev eth1 parent 1:50 handle 50:  sfq perturb 15
> >
> > tc qdisc add dev eth1 parent 1:12 handle 12:  sfq perturb 15
> > tc qdisc add dev eth1 parent 1:13 handle 13:  sfq perturb 15
> > tc qdisc add dev eth1 parent 1:14 handle 14:  sfq perturb 15
> >
> > tc filter add dev eth1 protocol ip parent 1: u32 match ip dst
> > 192.168.0.45 flowid 1:20
> >
> > tc filter add dev eth1 protocol ip parent 1: u32 match ip dst 192.168.0.4
> > flowid 1:30
> >
> > tc filter add dev eth1 protocol ip parent 1: u32 match ip dst
> > 192.168.0.50 flowid 1:40
> >
> > tc filter add dev eth1 protocol ip parent 1: u32 match ip dst
> > 192.168.0.38 flowid 1:50
> >
> > tc filter add dev eth1 protocol ip parent 1: prio 1 u32 match ip sport 80
> > 0xffff flowid 1:12
> > tc filter add dev eth1 protocol ip parent 1: prio 2 u32 match ip sport 25
> > 0xffff flowid 1:13
> > tc filter add dev eth1 protocol ip parent 1: prio 3 u32 match ip sport
> > 110 0xffff flowid 1:13
>


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

  reply	other threads:[~2003-02-20 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 21:40 [LARTC] limiting users on a 128kbit line radus
2003-02-20 14:17 ` radus [this message]
2003-02-20 16:10 ` Mathieu Deziel

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=marc-lartc-104575072331126@msgid-missing \
    --to=radus@rdsor.ro \
    --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.