All of lore.kernel.org
 help / color / mirror / Atom feed
From: Launchpad Bug Tracker <1228285@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1228285] Re: e1000 nic TCP performances
Date: Mon, 18 Jun 2018 04:17:38 -0000	[thread overview]
Message-ID: <152929545901.23342.13254026854170505639.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20130920172123.20190.55970.malonedeb@wampee.canonical.com

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1228285

Title:
  e1000 nic TCP performances

Status in QEMU:
  Expired

Bug description:
  Hi,

  Here is the context :

  $ qemu -name A -m 1024 -net nic vlan=0,model=e1000 -net socket,vlan=0,listen=127.0.0.1:7000
  $ qemu -name B -m 1024 -net nic vlan=0,model=e1000 -net socket,vlan=0,connect=127.0.0.1:7000

  The bandwidth is really tiny :

      . Iperf3 reports about 30 Mb/sec
      . NetPerf reports about 50 Mb/sec

  
  With UDP sockets, there is no problem at all :

      . Iperf3 reports about 1 Gb/sec
      . NetPerf reports about 950 Mb/sec

  
  I've noticed this fact only with the e1000 NIC, not with others (rtl8139,virtio, etc.)
  I've used the main GIT version of QEMU.

  
  Thanks in advance.

  See you,
  VInce

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1228285/+subscriptions

      parent reply	other threads:[~2018-06-18  4:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 17:21 [Qemu-devel] [Bug 1228285] [NEW] e1000 nic TCP performances Vincent Autefage
2013-09-23 13:43 ` Stefan Hajnoczi
2018-04-18 15:47 ` [Qemu-devel] [Bug 1228285] " Thomas Huth
2018-06-18  4:17 ` Launchpad Bug Tracker [this message]

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=152929545901.23342.13254026854170505639.malone@loganberry.canonical.com \
    --to=1228285@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.