All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marian Jancar marian.jancar@infonet.cz
To: lartc@vger.kernel.org
Subject: [LARTC] CBQ clases
Date: Wed, 17 Jan 2001 10:48:25 +0000	[thread overview]
Message-ID: <marc-lartc-98373940416893@msgid-missing> (raw)

<PRE>Im trying to create bounded class with two bouded childs, each one
having more than half bandwidth of their parent, whoose bandwidth they
should share, which sadly doesnt happen, when I tcpspray through both
childs in the same time, each one uses its full bandwidth, what is of
course togeather more, than bandwidth of their parent. Any suggesstions
wellcome.

tc qdisc add dev eth0 root handle 1: cbq bandwidth 10Mbit allot 1514
cell 8 avpkt 1000

#*******trida 64Kbit**********
tc class add dev eth0 parent 1:0 classid 1:200 cbq bandwidth 10Mbit rate
64Kbit allot 1514 cell 8 avpkt 1000 maxburst 20 weight 6Kbit prio 5
bounded

#*******trida 48Kbit**********
tc class add dev eth0 parent 1:200 classid 1:210 cbq bandwidth 10Mbit
rate 48Kbit allot 1514 cell 8 avpkt 1000 maxburst 20 weight 5Kbit prio 5
bounded
#tc qdisc add dev eth0 parent 1:210 red bandwidth 48Kbit min 4500 max
9000 limit 18000 avpkt 1000 burst 5 probability 0.02

#*******trida 48Kbit*********
tc class add dev eth0 parent 1:200 classid 1:220 cbq bandwidth 10Mbit
rate 48Kbit allot 1514 cell 8 avpkt 1000 maxburst 20 weight 5Kbit prio 5
bounded
#tc qdisc add dev eth0 parent 1:220 red bandwidth 48Kbit min 4500 max
9000 limit 18000 avpkt 1000 burst 5 probability 0.02

#Filtry
tc filter add dev eth0 parent 1:0 prio 5 protocol ip u32
tc filter add dev eth0 parent 1:0 prio 5 u32 divisor 256

tc filter add dev eth0 parent 1:0 prio 5 u32 match ip dst 10.0.0.2
flowid 1:210
tc filter add dev eth0 parent 1:0 prio 5 u32 match ip dst 10.0.0.3
flowid 1:220


</PRE>

                 reply	other threads:[~2001-01-17 10:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-98373940416893@msgid-missing \
    --to=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.