All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Vincent Autefage <1228285@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1228285] [NEW] e1000 nic TCP performances
Date: Mon, 23 Sep 2013 15:43:19 +0200	[thread overview]
Message-ID: <20130923134319.GB10376@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20130920172123.20190.55970.malonedeb@wampee.canonical.com>

On Fri, Sep 20, 2013 at 05:21:23PM -0000, Vincent Autefage wrote:
> 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.

It's interesting that you see good performance over -netdev socket TCP
with the other NIC models.

I don't know what the issue would be, you'll probably need to dig
further to discover the problem.  Using wireshark might be a good start.
Try to figure out where the delay is incurred and then instrument that
code to find out the cause.

Stefan

  reply	other threads:[~2013-09-24 11:23 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 [this message]
2018-04-18 15:47 ` [Qemu-devel] [Bug 1228285] " Thomas Huth
2018-06-18  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=20130923134319.GB10376@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=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.