From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:41993) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbEav-0006LG-S0 for qemu-devel@nongnu.org; Thu, 15 Dec 2011 11:55:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RbEau-0004K6-DU for qemu-devel@nongnu.org; Thu, 15 Dec 2011 11:55:45 -0500 Received: from indium.canonical.com ([91.189.90.7]:52108) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbEau-0004Jx-96 for qemu-devel@nongnu.org; Thu, 15 Dec 2011 11:55:44 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1RbEat-0004mY-7H for ; Thu, 15 Dec 2011 16:55:43 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 3610A2E8056 for ; Thu, 15 Dec 2011 16:55:43 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 15 Dec 2011 16:48:13 -0000 From: Vincent Autefage <899140@bugs.launchpad.net> Sender: bounces@canonical.com References: <20111202125742.13621.362.malonedeb@soybean.canonical.com> <20111202131025.12679.91449.launchpad@wampee.canonical.com> <4ED8E449.1010409@labri.fr> <4EDB98B2.6070408@labri.fr> <20111205082617.GA20569@stefanha-thinkpad.localdomain> <4EDCA13E.3080508@labri.fr> <4EE8B68F.4050003@labri.fr> <20111215080758.GA26425@stefanha-thinkpad.localdomain> <4EEA0CDA.80904@labri.fr> Message-Id: <4EEA25B0.8030705@labri.fr> Errors-To: bounces@canonical.com Subject: Re: [Qemu-devel] [Bug 899140] Re: Problem with Linux Kernel Traffic Control Reply-To: Bug 899140 <899140@bugs.launchpad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Here is the problem ! The Ubuntu version works only because it not uses an *Intel e1000* but a = *rtl8139*. Therefore, the problem about the e1000 is present in *all* version = (original or ubuntu ones). Thus, the file *e1000.c* must contain some instructions which imply the = bad TC behavior. Vincent Le 15/12/2011 17:09, Stefan Hajnoczi a =C3=A9crit : > On Thu, Dec 15, 2011 at 3:03 PM, Vincent Autefage > <899140@bugs.launchpad.net> wrote: >> Ok, >> >> So the e1000.c and the e1000_hw.h have absolutely no difference between >> the original and the ubuntu version... >> The only differences witch refers to the *Intel e1000* in the wall >> sources is this one : >> >> >> diff -ru qemu//hw/pc_piix.c qemu-kvm-0.14.0+noroms//hw/pc_piix.c >> --- qemu//hw/pc_piix.c 2011-12-15 15:37:28.539290000 +0100 >> +++ qemu-kvm-0.14.0+noroms//hw/pc_piix.c 2011-02-22 >> 14:34:38.000000000 +0100 >> >> @@ -123,7 +141,7 @@ >> if (!pci_enabled || (nd->model&& strcmp(nd->model, >> "ne2k_isa") =3D=3D 0)) >> pc_init_ne2k_isa(nd); >> else >> - pci_nic_init_nofail(nd, "e1000", NULL); >> + pci_nic_init_nofail(nd, "rtl8139", NULL); >> } >> >> if (drive_get_max_bus(IF_IDE)>=3D MAX_IDE_BUS) { > That looks like it is only changing the default NIC from e1000 to > rtl8139. > > Stefan > -- = 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 p= roblem 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 par= ticular 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 wi= th 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