From: Orlie Brewer <orlie.t.brewer@boeing.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb & bandwidth sharing
Date: Mon, 16 Jun 2003 17:34:41 +0000 [thread overview]
Message-ID: <marc-lartc-105578495114327@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105578333912260@msgid-missing>
We noted this problem that the first subclass got all the extra bandwidth
when the subclasses should be sharing the extra bandwidth equally.
We were able to get it working better by lowering the quantum to 1600.
I think what is happening with a larger quantum is that the first subclass
is getting all the extra bandwidth in one quantum.
Orlie
On Monday 2003.06.16 10:07 Albert Martorell wrote:
> Hi everybody!
>
> I've been trying with htb and tc filter. It seemed to work fine, but
> after testing with ethloop I've realized that traffic is not being
> distributed through the leaves as I thought. When sending packets to
> 1:10 and 1:11 at the same time, there's no bandwidth sharing. There's no
> traffic through 1:11 until traffic through 1:10 has finished. Though
> I've tried assigning different prio's, 1:10 always gets more
> bandwidth...
>
> Here's the script that reproduces this behaviour:
>
> tc qdisc add dev eth0 root handle 1: htb default 12 r2q 10
> tc class add dev eth0 parent 1: classid 1:1 htb rate 600kbit ceil
> 600kbit
> tc class add dev eth0 parent 1:1 classid 1:10 htb rate 200kbit ceil
> 600kbit
> tc class add dev eth0 parent 1:1 classid 1:11 htb rate 200kbit ceil
> 600kbit
> tc class add dev eth0 parent 1:1 classid 1:12 htb rate 200kbit ceil
> 600kbit
> tc qdisc add dev eth0 parent 1:10 handle 20: sfq perturb 10
> tc qdisc add dev eth0 parent 1:11 handle 21: sfq perturb 10
> tc qdisc add dev eth0 parent 1:12 handle 22: sfq perturb 10
>
> tc filter add dev eth0 protocol ip parent 1: u32 match ip sport 53
> 0xffff flowid 1:10
> tc filter add dev eth0 protocol ip parent 1: u32 match ip src 1.2.3.4
> match ip sport 80 0xffff flowid 1:11
>
>
> Thanks in advance!
>
> Albert
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-06-16 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 17:07 [LARTC] htb & bandwidth sharing Albert Martorell
2003-06-16 17:16 ` Stef Coene
2003-06-16 17:34 ` Orlie Brewer [this message]
2003-06-17 9:13 ` Albert Martorell
2003-06-17 13:35 ` Stef Coene
2003-06-17 15:43 ` Albert Martorell
2003-06-17 17:20 ` Stef Coene
2003-06-18 12:08 ` Albert Martorell
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-105578495114327@msgid-missing \
--to=orlie.t.brewer@boeing.com \
--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.