From: "Tom Olexa" <olexat@post.cz>
To: lartc@vger.kernel.org
Subject: [LARTC] Excess bandwidth sharing
Date: Wed, 08 Oct 2003 13:08:03 +0000 [thread overview]
Message-ID: <marc-lartc-106561858328271@msgid-missing> (raw)
Hello there,
I do
tc qdisc add dev eth0 root handle 1: htb r2q 1 default 12
tc class add dev eth0 parent 1:1 classid 1:10 htb rate 64kbit
ceil 512kbit tc class add dev eth0 parent 1:1 classid 1:11 htb
rate 256kbit ceil 512kbit
tc filter add dev eth0 parent 1: protocol ip prio 1 u32 \
match ip dst 195.28.103.7 flowid 1:10
tc filter add dev eth0 parent 1: protocol ip prio 1 u32 \
match ip dst 195.28.103.5 flowid 1:11
and I expect both streams to share the total 512kbit in
proportion of their rates (1/4). Unfortunately the rates are some
100/120, total 512kbit.
Can anyone tell me whatsda problem?
This behavior may vary when all rates are different.
Thanks, Tom Olexa
--
Potrebujete vice prostoru pro vase stranky?
Ptejte se na http://sluzby.volny.cz/cs/product/ftp_paid
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-10-08 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 13:08 Tom Olexa [this message]
2003-10-08 17:15 ` [LARTC] Excess bandwidth sharing Stef Coene
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-106561858328271@msgid-missing \
--to=olexat@post.cz \
--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.