All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timo Benk" <Timo.Benk@gmx.de>
To: xen-devel@lists.xensource.com
Subject: Linux Traffic Shaping broken in 3.0.3rc1 ?
Date: Sat, 07 Oct 2006 21:21:15 +0200	[thread overview]
Message-ID: <20061007192115.28680@gmx.net> (raw)

Hi,

with Xen 3.0.2 i used tc to limit the outgoing traffic rate and it
worked very well and accurate with the HTB class:

Limit: 1mbit / actual rate: 116.2KB/s (given by scp)


Now i looked at 3.0.3rc1 and noticed that traffic shaping using the same
setup as before does not work as accurate as before (same hardware):

Limit: 1mbit / actual rate: 449.0KB/s (given by scp)


Interstingly shaping of the incoming transfer rate at the vif*.*
interfaces works correct.

The problem is reproducible on my side and for me it seems to be a
problem with the new Xen-kernel.

Here is a stripped down version of my tc setup for you to verify the
problem:

----<snip>----
tc qdisc add dev peth0 root handle 1:0 htb
tc class add dev peth0 parent 1:0 classid 1:1 htb rate 1mbit
tc qdisc add dev peth0 parent 1:1 handle 11: prio
tc filter add dev peth0 parent 1:0 protocol ip prio 1 u32 match ip src \
  172.17.0.100/32 flowid 1:1
----<snap>----

172.17.0.100/32 is the IP of my Domain-0.

Greetings,
-timo
-- 
Timo Benk - B1 Systems GmbH (http://www.b1-systems.de) 
Jabber ID: fry@jabber.org - ICQ ID: #241877854 
PGP Public Key: http://m28s01.vlinux.de/b1_gpg_key.asc

             reply	other threads:[~2006-10-07 19:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07 19:21 Timo Benk [this message]
2006-10-08 16:17 ` Linux Traffic Shaping broken in 3.0.3rc1 ? Matt Ayres
2006-10-08 17:07   ` Keir Fraser
2006-10-08 18:30     ` Timo Benk
2006-10-09 12:38       ` Keir Fraser
2006-10-09 16:18       ` Keir Fraser
2006-10-10 10:16         ` Keir Fraser
2006-10-10 10:50           ` Timo Benk
2006-10-10 11:36             ` Keir Fraser
2006-10-10 12:50         ` Keir Fraser
2006-10-09 15:40 ` Keir Fraser

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=20061007192115.28680@gmx.net \
    --to=timo.benk@gmx.de \
    --cc=xen-devel@lists.xensource.com \
    /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.