From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] my qos-cbq didn't work
Date: Fri, 13 Dec 2002 17:04:50 +0000 [thread overview]
Message-ID: <marc-lartc-103979934220986@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103973481703733@msgid-missing>
On Friday 13 December 2002 00:09, James Ma wrote:
> Hi, All,
>
> I implemented the following qos scripts in my Linux gateway (redhat7.3,
> kernel 2.4.18), put ftp server (10.10.3.49) on one side (eth0 nic) and ftp
> client (10.10.5.3) on the other side (eth1 nic). I tried to up load a file
> (211kbytes) from client to ftp server. I wanted to see a 22kbps
> transmission rate. Quite surprise, the ftp client showed transmission rate
> as 6.8e+02 kbytes/s (211k transmitted in 0.3 seconds). It was the same as
> it without qos implementation. So the conclusion is the QoS was not working
> at all.
>
> Could anybody tell me what's wrong with the setting?
Yes I can. You have a cbq qdisc attached to a cbq class. This will cause
some problems. I did some test about this (www.docum.org on the test page).
It's better to create only classes :
tc qdisc add dev eth0 root handle 10: cbq bandwidth 10mbit avpkt 500
tc class add dev eth0 parent 10:0 classid 10:2 cbq bandwidth 10mbit rate
22kbps $OPTION prio 3 bounded
tc class add dev eth0 parent 10:2 classid 10:10 cbq bandwidth 10mbit rate
11kbps $OPTION prio 3 bounded
tc class add dev eth0 parent 10:2 classid 10:20 cbq bandwidth 10mbit rate
11kbps $OPTION prio3 bounded
If you bound 10:10 and 10:20 they are not able to borrow bandwidth from each
other.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-13 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 23:09 [LARTC] my qos-cbq didn't work James Ma
2002-12-13 17:04 ` Stef Coene [this message]
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-103979934220986@msgid-missing \
--to=stef.coene@docum.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox