From: Lorenzo Allegrucci <l.allegrucci@gmail.com>
To: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Strange traffic control behaviour?
Date: Fri, 6 Feb 2009 09:43:23 +0100 [thread overview]
Message-ID: <4dcf7d360902060043y7d11b9d7m94af9f7d06862660@mail.gmail.com> (raw)
Hi, I noticed a strange behaviour on a small sample network I used to test my
traffic control setup.
Below is the network setup (sorry for my ascii art..):
end user1|------------|router1|------------|router2|------------|end user2|
eth0 eth1 eth0 eth0 eth1 eth0
(Static routes on router1 and router2).
Test1:
I applied the following tc rules on eth1 of router1 to limit the bandwidth
to 3Mbit for a download flux (by wget or scp) from "end user2" to "end user1":
tc qdisc add dev eth1 root handle 1:0 htb default 100
tc class add dev eth1 parent 1:0 classid 1:1 htb rate 3Mbit ceil 3Mbit
tc class add dev eth1 parent 1:1 classid 1:100 htb rate 2Mbit ceil 3Mbit
tc class add dev eth1 parent 1:1 classid 1:200 htb rate 1Mbit ceil 3Mbit
Theoretically "end user1" should get about 375kbyte/s (3Mbit), but instead
I get bit less, about 330 kbye/s and the flux tends to fluctuate a bit.
(all other interfaces are "clean", no tc rules).
Test2:
However, if I apply the same tc rules to the router2's eth0 instead, I get
a *stable* flux of *exactly* 3Mbit (375kbyte/s), to be more precise what
I should have gotten on test1!
How can this be explained?
In general, noticed that tc applied "upstream" gives better results than
tc applied downstream. In other words, it's better to limit network
traffic near the source, can you confirm?
Thanks.
--
Lorenzo
reply other threads:[~2009-02-06 8:43 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=4dcf7d360902060043y7d11b9d7m94af9f7d06862660@mail.gmail.com \
--to=l.allegrucci@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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
all inboxes | Powered by JetHome®