From: xiao hongge <xhongge@yahoo.com>
To: lartc@vger.kernel.org
Subject: [LARTC] why? cbq vs htb on FTP server.
Date: Tue, 08 Oct 2002 08:10:22 +0000 [thread overview]
Message-ID: <marc-lartc-103407776109992@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
On linux box that with QOS and ftpd.
The QOS with either CBQ or HTB qdisc,the result was different.
With CBQ on linux box,and a class setup 70kB.
The ftp client download a file from linux box.
a) linux os,the download bandwidth is 68kB.
b) win98 os,the download bandwidth is 68kB.
Script:
#!/bin/sh
tc qdisc del dev eth0 root handle 1:
tc qdisc add dev eth0 root handle 1: cbq bandwidth 100mbit avpkt 1000
tc class add dev eth0 parent 1: classid 1:1 cbq bandwidth 100mbit rate 100mbit maxburst 21 allot 1514 avpkt 1000 prio 7
tc class add dev eth0 parent 1:1 classid 1:70 cbq bandwidth 100mbit rate 560kbit maxburst 21 allot 1514 avpkt 1000 prio 6 bounded
tc filter add dev eth0 parent 1: protocol ip prio 3 handle 2 fw classid 1:70
ipchains -F
ipchains -I output -d clinetA -m 2 -j ACCEPT
With HTB on linux box,and a class setup 70kB.
The ftp client download a file from linux box.
a) linux os,the download bandwidth is 68kB.
b) win98 os,the download bandwidth is 26kB.
Script:
#!/bin/sh
#
tc qdis del dev eth0 root handle 1:
tc qdisc add dev eth0 root handle 1: htb default 12
tc class add dev eth0 parent 1: classid 1:1 htb rate 100kbps ceil 100kbps burst 2k
tc class add dev eth0 parent 1:1 classid 1:70 htb rate 70kbps ceil 70kbps burst 2k
tc filter add dev eth0 parent 1: protocol ip prio 3 handle 2 fw classid 1:70
ipchains -F
ipchains -I output -d clinetA -m 2 -j ACCEPT
---------------------------------
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos, & more
faith.yahoo.com
[-- Attachment #2: Type: text/html, Size: 1749 bytes --]
reply other threads:[~2002-10-08 8:10 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-103407776109992@msgid-missing \
--to=xhongge@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox