From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH-RFC 00/13] vhost-net: preview
Date: Mon, 11 Jan 2010 20:09:10 +0000 [thread overview]
Message-ID: <20100111200910.GB10230@redhat.com> (raw)
In-Reply-To: <20100111171641.GA11936@redhat.com>
On Mon, Jan 11, 2010 at 07:16:42PM +0200, Michael S. Tsirkin wrote:
> Here's an untested patchset with vhost support for upstream qemu. Note
> that you should not expect performance gains from vhost unless in-kernel
> irqchip is enabled (which is not in upstream qemu now). Since adding
> vhost involves quite a bit of infrastructure, I thought it makes sense
> to send an RFC already, so that interested parties can review it. In
> particular, command line and help text need to be finalized early to so
> that management can start looking on supporting the feature. This patch
> has all bits besides migration filled in. Also missing is packet socket
> backend: another team is now working on this.
Can you clarify a question about migration for me. Is it possible to
live migrate a guest configured with tap + bridge on one machine over
to another where it is launched with vhost + bridge, and vice-versa.
In other words does this vhost support have any guest visible impact
that would cause migraiton compatability problems, or it is purely a
host side optimization like vnet_hdr was ?
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2010-01-11 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 17:16 [Qemu-devel] [PATCH-RFC 00/13] vhost-net: preview Michael S. Tsirkin
2010-01-11 20:09 ` Daniel P. Berrange [this message]
2010-01-11 20:15 ` 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=20100111200910.GB10230@redhat.com \
--to=berrange@redhat.com \
--cc=mst@redhat.com \
--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).