qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Webb <chris@arachsys.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: netdev@vger.kernel.org, Jason Wang <jasowang@redhat.com>,
	qemu-devel@nongnu.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [Qemu-devel] Slow inbound traffic on macvtap interfaces
Date: Thu, 16 Aug 2012 15:27:57 +0100	[thread overview]
Message-ID: <20120816142756.GA9806@arachsys.com> (raw)
In-Reply-To: <20120816114233.GA21343@redhat.com>

"Michael S. Tsirkin" <mst@redhat.com> writes:

> On Thu, Aug 16, 2012 at 10:20:05AM +0100, Chris Webb wrote:
>
> > For example, I can run
> > 
> >   ip addr add 192.168.1.2/24 dev eth0
> >   ip link set eth0 up
> >   ip link add link eth0 name tap0 address 02:02:02:02:02:02 type macvtap mode bridge
> >   ip link set tap0 up
> >   qemu-kvm -hda debian.img -cpu host -m 512 -vnc :0 \
> >     -net nic,model=virtio,macaddr=02:02:02:02:02:02 \
> >     -net tap,fd=3 3<>/dev/tap$(< /sys/class/net/tap0/ifindex)
> > 
> > on one physical host which is otherwise completely idle. From a second
> > physical host on the same network, I then scp a large (say 50MB) file onto
> > the new guest. On a gigabit LAN, speeds consistently drop to less than
> > 100kB/s as the transfer progresses, within a second of starting.

> Thanks for the report.
> I'll try to reproduce this early next week.
> Meanwhile a question - do you still observe this behaviour if you enable
> vhost-net?

I haven't tried running with vhost-net before. Is it sufficient to compile
the host kernel with CONFIG_VHOST_NET=y and boot the guest with

  qemu-kvm -hda debian.img -cpu host -m 512 -vnc :0 \
    -net nic,model=virtio,macaddr=02:02:02:02:02:02 \
    -net tap,fd=3,vhost=on,vhostfd=4 \
    3<>/dev/tap$(< /sys/class/net/tap0/ifindex) 4<>/dev/vhost-net

? If so, then I'm afraid this doesn't make any difference: it still stalls
and drops right down in speed.

The reason I'm hesitant about whether the vhost-net is actually working is
that with both vhost=off and vhost=on, I see an identical virtio feature set
within the guest:

  # cat /sys/bus/virtio/devices/virtio0/features 
  0000011000000001111100000000100000000000000000000000000000000000

However, without the 4<>/dev/vhost-net or with 4<>/dev/null, it seems to
fail to start altogether with vhost=on,vhostfd=4, so perhaps it's fine?

Cheers,

Chris.

  reply	other threads:[~2012-08-16 14:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  9:20 [Qemu-devel] Slow inbound traffic on macvtap interfaces Chris Webb
2012-08-16 11:42 ` Michael S. Tsirkin
2012-08-16 14:27   ` Chris Webb [this message]
2012-08-16 15:36     ` Michael S. Tsirkin
2012-09-19 15:11       ` [Qemu-devel] Macvtap bug: contractor wanted Richard Davies, Chris Webb
2012-09-19 17:54         ` David Miller
2012-08-29 17:52 ` [Qemu-devel] Slow inbound traffic on macvtap interfaces Chris Webb
2012-08-30  8:20   ` Richard Davies
2012-08-30  8:44     ` Michael S. Tsirkin

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=20120816142756.GA9806@arachsys.com \
    --to=chris@arachsys.com \
    --cc=arnd@arndb.de \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).