From: "openings" <openings@palgong.knu.ac.kr>
To: lartc@vger.kernel.org
Subject: [LARTC] can't guaranteed to TCP traffic with HTB
Date: Sun, 01 Jun 2003 19:46:17 +0000 [thread overview]
Message-ID: <marc-lartc-105449687715755@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105449659515510@msgid-missing>
Hi.
What I want
====I want to guarantee bandwidth of TCP traffic when there is background UDP traffic.
Testbed setting
=====webserver---1---- ---5----- Host 1
| |
+----3----- Linux TC ----4-----+
| |
UDP src-----2--- eth0 eth1 ---6-----Host 2
Link speed
====
1, 2, 4, 5, 6 : 10Mbps
3 : 100Mbps
Traffic Generation
======"UDP src" machine generate background UDP traffic at 10Mbps to Host 1.(generator : MGEN 4.0)
Host 1 and Host 2 Download files from "webserver" by HTTP. (TCP traffic)
Seudo tc command
======add qdisc dev eth1 root handle 1: htb default 2
add class dev eth1 parent 1: classid 1:1 rate 10Mbit ceil 10Mbit
add class dev eth1 parent 1:1 classid 1:2 rate 1Mbit ceil 9Mbit <== UDP traffic
add class dev eth1 parent 1:1 classid 1:3 rate 3Mbit ceil 3Mbit <== TCP traffic of Host 1
add class dev eth1 parent 1:1 classid 1:4 rate 1Mbit ceil 1Mbit <== TCP traffic of Host 2
Problem
===
I want to guarantee Host1 TCP and Host 2 TCP traffic by rate value. (3Mbps, 1Mbps)
but when I start test, UDP traffic dominate 9Mbps speed. (it used full of ceil rate)
the ramainder bandwidth is divided by Host1 TCP and Host2 TCP. (very slow!)
Why TCP traffic can't get bandwidth of rate setting.?
UDP traffic's rate value is 1Mbos, nevertheless UDP traffic get 9Mbps.
Why rate value is not guaranteed to TCP traffic class ?ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿË\x01\x14™¨¥Šx%ŠË\x7f,\x04S\vùšŠYšŸ÷lõ¯ç–^[m§ÿÿ™¨¥™©ÿvÏZþy\x7f™¨¥™©ÿ–+-ŠwèþV«µÁÎY3ÿ†Ûiÿÿåj»\þŠà
next prev parent reply other threads:[~2003-06-01 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 19:41 [LARTC] can't guaranteed to TCP traffic with HTB openings
2003-06-01 19:46 ` openings [this message]
2003-06-01 21:19 ` Goetz von Escher
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-105449687715755@msgid-missing \
--to=openings@palgong.knu.ac.kr \
--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.