From: Stefan Hajnoczi <stefanha@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: wei.w.wang@intel.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vhost-pci and virtio-vhost-user
Date: Thu, 18 Jan 2018 10:51:03 +0000 [thread overview]
Message-ID: <20180118105103.GC19831@stefanha-x1.localdomain> (raw)
In-Reply-To: <9fad276a-d17b-6a45-6cd6-50899934b7a1@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2264 bytes --]
On Tue, Jan 16, 2018 at 01:41:37PM +0800, Jason Wang wrote:
>
>
> On 2018年01月15日 21:56, Stefan Hajnoczi wrote:
> > On Mon, Jan 15, 2018 at 02:56:31PM +0800, Jason Wang wrote:
> > > On 2018年01月12日 18:18, Stefan Hajnoczi wrote:
> > > > > And what's more important, according to the kvm 2016 slides of vhost-pci,
> > > > > the motivation of vhost-pci is not building SDN but a chain of VNFs. So
> > > > > bypassing the central vswitch through a private VM2VM path does make sense.
> > > > > (Though whether or not vhost-pci is the best choice is still questionable).
> > > > This is probably my fault. Maybe my networking terminology is wrong. I
> > > > consider "virtual network functions" to be part of "software-defined
> > > > networking" use cases. I'm not implying there must be a central virtual
> > > > switch.
> > > >
> > > > To rephrase: vhost-pci enables exitless VM2VM communication.
> > > The problem is, exitless is not what vhost-pci invents, it could be achieved
> > > now when both sides are doing busypolling.
> > The only way I'm aware of is ivshmem. But ivshmem lacks a family of
> > standard device types that allows different implementations to
> > interoperate. We already have the virtio family of device types, so it
> > makes sense to work on a virtio-based solution.
> >
> > Perhaps I've missed a different approach for exitless VM2VM
> > communication. Please explain how VM1 and VM2 can do exitless network
> > communication today?
>
> I'm not sure we're talking the same thing. For VM2VM, do you mean only for
> shared memory? I thought we can treat any backends that can transfer data
> directly between two VMs for a VM2VM solution. In this case, if virtqueue
> notifications were disabled by all sides (e.g busy polling), there will be
> no exits at all.
>
> And if you want a virtio version of shared memory, it's another kind of
> motivation at least from my point of view.
I'm confused, we're probably not talking about the same thing.
You said that exitless "could be achieved now when both sides are doing
busypolling". Can you post a QEMU command-line that does this?
In other words, what exactly are you proposing as an alternative to
vhost-pci?
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-01-18 10:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 16:14 [Qemu-devel] vhost-pci and virtio-vhost-user Stefan Hajnoczi
2018-01-11 6:31 ` Wei Wang
2018-01-11 9:56 ` Stefan Hajnoczi
2018-01-12 6:44 ` Wei Wang
2018-01-12 10:37 ` Stefan Hajnoczi
2018-01-14 3:36 ` Wang, Wei W
2018-01-15 14:02 ` Stefan Hajnoczi
2018-01-11 10:57 ` Jason Wang
2018-01-11 15:23 ` Stefan Hajnoczi
2018-01-12 3:32 ` Jason Wang
2018-01-12 5:20 ` Yang, Zhiyong
2018-01-15 3:09 ` Jason Wang
2018-01-12 10:18 ` Stefan Hajnoczi
2018-01-15 6:56 ` Jason Wang
2018-01-15 7:59 ` Wei Wang
2018-01-15 8:34 ` Jason Wang
2018-01-15 10:43 ` Wei Wang
2018-01-16 5:33 ` Jason Wang
2018-01-17 8:44 ` Wei Wang
2018-01-15 13:56 ` Stefan Hajnoczi
2018-01-16 5:41 ` Jason Wang
2018-01-18 10:51 ` Stefan Hajnoczi [this message]
2018-01-18 11:51 ` Jason Wang
2018-01-19 17:20 ` Stefan Hajnoczi
2018-01-22 3:54 ` Jason Wang
2018-01-23 11:52 ` Stefan Hajnoczi
2018-01-15 7:56 ` Wei Wang
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=20180118105103.GC19831@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wei.w.wang@intel.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 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).