From: Vincent Autefage <899140@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 899140] Re: Problem with Linux Kernel Traffic Control
Date: Mon, 30 Jan 2012 16:30:45 -0000 [thread overview]
Message-ID: <4F26C5C6.2090505@labri.fr> (raw)
In-Reply-To: 20120129044901.6982.30037.malone@soybean.canonical.com
Hi,
The problem seems to come from the implementation of the Intel e1000
network cards (which is the default one used by QEMU).
If you use another one, the problem does not appear ;)
Vince
Le 29/01/2012 05:49, Henrique Rodrigues a écrit :
> Hi guys,
>
> I'm having the same problem with a ubuntu 11.04 (natty) host. I tried to
> set the rate controllers using tc both at the host and inside the guest
> i.e.:
>
> tc qdisc add vnic0 root tbf rate 20mbit burst 20480 latency 50ms (host - to control the traffic going to the guest vm) and
> tc qdisc add eth0 root tbf rate 20mbit burst 20480 latency 50ms (guest)
>
> And the results are the same reported initially: ~140kbit/sec. I also
> tried to use policing filters at the host but I got the same results.
>
> However, if I use htb I can get reasonable throughputs (~20mbit). I used
> these commands (both for host and guest):
>
> tc qdisc add dev<DEV> root handle 1: htb default 255
> tc class add dev<DEV> parent 1: classid 1:1 htb rate 20mbit burst 20480
> tc filter add dev<DEV> parent 1: prio 255 proto ip u32 match ip src 0.0.0.0/0 flowid 1:1
>
> It seems that the problem is related with the root qdisc only. Have you
> guys found an answer for this?
>
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/899140
Title:
Problem with Linux Kernel Traffic Control
Status in QEMU:
New
Bug description:
Hi,
The last main versions of QEMU (0.14.1, 0.15 and 1.0) have an important problem when running on a Linux distribution which running itself a Traffic Control (TC) instance.
Indeed, when TC is configured with a Token Bucket Filter (TBF) with a particular rate, the effective rate is very slower than the desired one.
For instance, lets consider the following configuration :
# tc qdisc add dev eth0 root tbf rate 20mbit burst 20k latency 50ms
The effective rate will be about 100kbit/s ! (verified with iperf)
I've encountered this problem on versions 0.14.1, 0.15 and 1.0 but not with the 0.14.0...
In the 0.14.0, we have a rate of 19.2 mbit/s which is quiet normal.
I've done the experimentation on several hosts :
- Debian 32bit core i7, 4GB RAM
- Debian 64bit core i7, 8GB RAM
- 3 different high performance servers : Ubuntu 64 bits, 48 AMD Opteron, 128GB of RAM
The problem is always the same... The problem is also seen with a
Class Based Queuing (CBQ) in TC.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/899140/+subscriptions
next prev parent reply other threads:[~2012-01-30 16:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 12:57 [Qemu-devel] [Bug 899140] [NEW] Problem with Linux Kernel Traffic Control Vincent Autefage
2011-12-02 13:10 ` [Qemu-devel] [Bug 899140] " Vincent Autefage
2011-12-02 13:34 ` Stefan Hajnoczi
2011-12-02 14:42 ` Vincent Autefage
2011-12-03 18:48 ` Stefan Hajnoczi
2011-12-04 15:54 ` Vincent Autefage
2011-12-05 8:26 ` Stefan Hajnoczi
2011-12-05 10:45 ` Vincent Autefage
2011-12-05 11:11 ` Stefan Hajnoczi
2011-12-05 12:24 ` Vincent Autefage
2011-12-07 10:57 ` Vincent Autefage
2011-12-14 13:36 ` Vincent Autefage
2011-12-14 14:32 ` Stefan Hajnoczi
2011-12-14 14:27 ` Vincent Autefage
2011-12-14 14:42 ` Vincent Autefage
2011-12-15 8:07 ` Stefan Hajnoczi
2011-12-15 15:03 ` Vincent Autefage
2011-12-15 16:09 ` Stefan Hajnoczi
2011-12-15 16:12 ` Stefan Hajnoczi
2011-12-15 16:48 ` Vincent Autefage
2011-12-16 8:31 ` Stefan Hajnoczi
2012-01-29 4:49 ` Henrique Rodrigues
2012-01-30 16:30 ` Vincent Autefage [this message]
2012-01-31 4:49 ` Henrique Rodrigues
2012-02-09 19:05 ` Henrique Rodrigues
2012-02-10 9:25 ` Vincent Autefage
2017-02-07 12:47 ` Thomas Huth
2017-04-09 4:17 ` Launchpad Bug Tracker
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=4F26C5C6.2090505@labri.fr \
--to=899140@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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.