From: "Michael S. Tsirkin" <mst@redhat.com>
To: Qin Chuanyu <qinchuanyu@huawei.com>
Cc: jasowang@redhat.com, kvm@vger.kernel.org, netdev@vger.kernel.org,
qianhuibin@huawei.com
Subject: Re: Is fallback vhost_net to qemu for live migrate available?
Date: Tue, 27 Aug 2013 07:19:35 +0300 [thread overview]
Message-ID: <20130827041935.GA7263@redhat.com> (raw)
In-Reply-To: <521C1DCF.5090202@huawei.com>
On Tue, Aug 27, 2013 at 11:32:31AM +0800, Qin Chuanyu wrote:
> Hi all
>
> I am participating in a project which try to port vhost_net on Xen。
>
> By change the memory copy and notify mechanism ,currently
> virtio-net with vhost_net could run on Xen with good
> performance。TCP receive throughput of single vnic from 2.77Gbps up
> to 6Gps。In VM receive side,I instead grant_copy with grant_map +
> memcopy,it efficiently reduce the cost of grant_table spin_lock of
> dom0,So the hole server TCP performance from 5.33Gps up to 9.5Gps。
>
> Now I am consider the live migrate of vhost_net on Xen,vhost_net
> use vhost_log for live migrate on Kvm,but qemu on Xen havn't manage
> the hole memory of VM,So I am trying to fallback datapath from
> vhost_net to qemu when doing live migrate ,and fallback datapath
> from qemu to
> vhost_net again after vm migrate to new server。
>
> My question is:
> why didn't vhost_net do the same fallback operation for live
> migrate on KVM,but use vhost_log to mark the dirty page?
> Is there any mechanism fault for the idea of fallback datapath from
> vhost_net to qemu for live migrate?
>
> any question about the detail of vhost_net on Xen is welcome。
>
> Thanks
>
It should work, in practice.
However, one issue with this approach that I see is that you
are running two instances of virtio-net on the host:
qemu and vhost-net, doubling your security surface
for guest to host attack.
I don't exactly see why does it matter that qemu doesn't manage
the whole memory of a VM - vhost only needs to log
memory writes that it performs.
next prev parent reply other threads:[~2013-08-27 4:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 3:32 Is fallback vhost_net to qemu for live migrate available? Qin Chuanyu
2013-08-27 4:19 ` Michael S. Tsirkin [this message]
2013-08-27 7:04 ` Qin Chuanyu
2013-08-27 7:16 ` Michael S. Tsirkin
2013-08-27 7:22 ` Qin Chuanyu
2013-08-27 9:41 ` Wei Liu
2013-08-29 16:08 ` Anthony Liguori
2013-08-31 4:45 ` Qin Chuanyu
2013-09-02 3:19 ` Jason Wang
2013-09-02 3:19 ` Jason Wang
2013-09-02 7:57 ` Wei Liu
2013-09-02 8:11 ` Michael S. Tsirkin
2013-09-02 8:11 ` Michael S. Tsirkin
2013-09-03 1:28 ` Qin Chuanyu
2013-09-03 1:28 ` Qin Chuanyu
2013-09-03 8:40 ` Wei Liu
2013-09-03 8:55 ` Michael S. Tsirkin
2013-09-03 8:55 ` Michael S. Tsirkin
2013-09-03 9:15 ` Wei Liu
2013-09-03 9:15 ` Wei Liu
2013-09-05 13:33 ` Stefano Stabellini
2013-09-05 13:33 ` [Xen-devel] " Stefano Stabellini
2013-09-03 8:40 ` Wei Liu
2013-09-02 7:57 ` Wei Liu
2013-08-31 4:45 ` Qin Chuanyu
2013-10-14 8:19 ` Qin Chuanyu
2013-10-14 8:19 ` Qin Chuanyu
2013-08-29 16:08 ` Anthony Liguori
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=20130827041935.GA7263@redhat.com \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qianhuibin@huawei.com \
--cc=qinchuanyu@huawei.com \
/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.